Opened 9 years ago

Closed 9 years ago

#2073 closed defect (implemented)

404 document doesn't work for subdirectories

Reported by: Sebastian Owned by: phobos
Priority: Medium Milestone:
Component: Webpages/Website Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

The issue is that the link to the css and images generated by head.wmi is relative to the subdir that wml expects to find the file in. That works for files that aren't aliased from other locations (like the normal website); but doesn't work for files that will be served from different parts of the directory structure.

Just changing the paths to always start with a / in our directory structure would solve this for us; but mirrors that might not have our website start in their root would break. I'm not sure what the solution is here.

To see what I mean, https://www.torproject.org/faq/faq

Child Tickets

Change History (5)

comment:1 Changed 9 years ago by arma

It's not just css and images, it's the links too. From your URL above, click on the 'tor users' link:

https://www.torproject.org/docs/faq/about/torusers.html.en

comment:2 Changed 9 years ago by arma

How about making our 404 doc be a 302 to a sitemap.html page?

Rather than having the 404 document pretend to be every possible page you could ask for.

(Maybe we want a 301; I'm not sure.)

comment:3 Changed 9 years ago by phobos

The best answer is the one no one liked originally, serve up a real 404. We do not want a 301, nor really a 302. Mainly, search engines and browsers will consider the 30x code as the new location of the content---which is not what we want. Now that we're sliding down the slippery slope of redirects, the 404-intercept-sitemap page is useless and confusing.

comment:4 Changed 9 years ago by phobos

I'll remove the sitemap.wml redirect from vescum.

comment:5 Changed 9 years ago by phobos

Resolution: implemented
Status: newclosed

done.

Note: See TracTickets for help on using tickets.