#dev 2026-01-15

2026-01-15 UTC
doesnm_ joined the channel
#
osteophage ulhar4409[d]: ulhar4409[d] https://blog.neocities.org/blog/2022/12/30/cleaner-links
#
ulhar4409 yea
#
ulhar4409 not *quite* applicable, considering they're using nginx
#
ulhar4409 whereas i'm trying to use .htaccess files
#
gRegor Not sure there's a way around that in Apache if `example/` is actually a directory
[bunnyguy] and [KevinMarks] joined the channel
#
[morgan] Ive been aware of web mentions for a while but never found a good time to put them in place, but I think with my new coffee crawl website I want to have the potential for web mentions
#
[morgan] Ill follow up with queryies after I look into it more
#
gRegor Oh, maybe not. I should have searched first. Maybe this directive: https://httpd.apache.org/docs/current/mod/mod_dir.html#directoryslash
#
gRegor Note the security warning there
#
[tantek] I disallow a plain trailing slash unless there's actually a usecase for putting something after it. e.g. my /pay page has a trailing slash, my /contact page does not (it 404s with a trailing slash)
CrimeWave joined the channel
#
ulhar4409 huh interesting
#
ulhar4409 ok actually, neocities nginx rules are simpler than i thought; they don't handle the "finding the right file" part, only regex-ing the request path
gRegor, gRegorLove_ and doesnm_ joined the channel
#
gRegor [tantek], even with directories, or only the rewritten URLs like your contact.html example above?
#
[tantek] directories should work fine with the trailing slash yeah
#
[tantek] however if it is "merely" a top level page, then I don't bother with the trailing slash
#
[tantek] similar to how our wiki works
#
[tantek] e.g. https://indieweb.org/IndieWeb works and https://indieweb.org/IndieWeb/ gives a 404 because they're different
#
gRegor makes sense
#
[tantek] same thing on Wikipedia etc. I figure if it's good enough for Wikipedia to reject trailing slashes on page names then I don't need to worry about it
#
gRegor I need to move away from trailing slash on my URLs. ProcessWire has an option for it but I didn't think about it when I set up my site ages ago. Thankfully it handles redirects for those nicely.
doesnm_ joined the channel
#
ulhar4409 got redirect chain going from /test/index.html -> /test/ -> /test but having trouble getting it to display the index.html from there
#
gRegor Is DirectoryIndex set?
#
ulhar4409 i am not sure if that's relevant here? i think that would only apply if the request had a trailing slash, and here the client is being coerced into Not doing that; but otherwise yes
#
[tantek] FWIW I found DirectoryIndex to be unreliable in lightspeed (which otherwise tries to support Apache htaccess files)
[Sophia_wood] joined the channel
#
ulhar4409 afaik i am just using regular apache (my host runs it out of the box)
doesnm_ joined the channel
#
gRegor DirectoryIndex should be what makes `/` render the index.html, same should apply if you have DirectorySlashes off
#
gRegor afaik, with no DirectoryIndex set, it would only be accessible by `/index.html`
#
gRegor (or rather, with DirectoryIndex off)
#
gRegor Most Apache setups I think default to `DirectoryIndex index.html` though, so it would be odd if it wasn't set already.
#
[aciccarello] Netlify normalizes to all trailing slashes
gRegor, DanQ, doesnm_, jjuran_ and [jeremycherfas] joined the channel
#
[jeremycherfas] Does anyone know whether `/ig.html` is some kind of vulnerability in websites? I’m seeing a lot of requests for that from my nemesis spam bots.
#
ulhar4409 hmm, .htaccess works fine without the "chop index.html off the URL" rule (was redirect-looping before)
#
ulhar4409 okay, i tried putting [END] on the final step and it seems to kick out of the loop
geraldd, jjuran, ttybitnik, gRegor, gRegorLove_ and GuestZero joined the channel