Authentication-Results: mail-b.sr.ht; dkim=none Received: from mout-p-202.mailbox.org (mout-p-202.mailbox.org [80.241.56.172]) by mail-b.sr.ht (Postfix) with ESMTPS id EBE3311EF1D for <~sircmpwn/sr.ht-discuss@lists.sr.ht>; Sun, 7 Mar 2021 21:35:08 +0000 (UTC) Received: from smtp1.mailbox.org (smtp1.mailbox.org [80.241.60.240]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-202.mailbox.org (Postfix) with ESMTPS id 4Dtvrr09LlzQjn9; Sun, 7 Mar 2021 22:35:08 +0100 (CET) X-Virus-Scanned: amavisd-new at heinlein-support.de Received: from smtp1.mailbox.org ([80.241.60.240]) by spamfilter04.heinlein-hosting.de (spamfilter04.heinlein-hosting.de [80.241.56.122]) (amavisd-new, port 10030) with ESMTP id RR8Q4EsDmC6d; Sun, 7 Mar 2021 22:35:01 +0100 (CET) Message-ID: Date: Mon, 8 Mar 2021 10:34:57 +1300 MIME-Version: 1.0 Subject: Re: [pages] Behaviour of Links Content-Language: en-US To: Drew DeVault , ~sircmpwn/sr.ht-discuss@lists.sr.ht References: <20210307092859.epjy2rpc6svzblxa@arch> From: "Webmaster At Solarpunk.Cool" In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-MBO-SPAM-Probability: ** X-Rspamd-Score: 2.52 / 15.00 / 15.00 X-Rspamd-Queue-Id: B469F185F X-Rspamd-UID: a6313b > The markup validates, but it's wrong. Your URL needs to point to the appropriate address I've updated my example to show the issue I'm having: https://solarpunk.cool/example The images will only load if I go to: https://solarpunk.cool/example/ or if i go to: https://solarpunk.cool/example/index.html --- It is likely that site visitors will not remember to add a trailing slash when visiting parts of the page. Coincidentally, I received an email this morning from someone reporting that https://solarpunk.cool/zines/web-zine-01 was broken (of course, https://solarpunk.cool/zines/web-zine-01/ works fine). Is it expected that I should add only absolute paths throughout the site to anticipate someone forgetting to add a trailing slash, or is it possible to have this redirect built into the server?  I am fine if the answer is the former, I just wanted to know if it's an issue in how I'm using relative links, or if I needed to adjust my assumptions on how sourcehut pages work. On 3/8/21 10:05 AM, Drew DeVault wrote: > The markup validates, but it's wrong. Your URL needs to point to the > appropriate address. The image is not at the location you have put into > the src attribute.