Ticket #258 (new defect)

Opened 8 years ago

Last modified 4 years ago

Sending 404 and 403 headers

Reported by: NilsLindenberg Owned by: unassigned
Priority: normal Milestone: 1.4
Component: architecture Version: 1.1.6.2
Severity: normal Keywords: 404 403 robot http header acls
Cc:

Description (last modified by DarTar) (diff)

copied from SuggestionBox --NilsLindenberg

Right now (1.1.6.0), if a non-existant page is requested, the wiki returns status code 200, which will cause the page to be indexed by search engine spiders. It'd probably be better to return 404 (not found) or 410 (gone) or include robots exclusion meta tags in the pages that don't exist. --BarkerJr

Ah, maybe this is why a now non-existent page that I deleted 2 months ago is still getting 50hits or so a day from the porn/vicodin/viagra sites that linked to it (don't ask //me// why...it was a completely inoccuous page)...at least according to the referrers database table. --GmBowen


For pages to which the user has no read-access, do you think it might be feasible/interesting to send - along with the //You aren't allowed to read this page// message - a HTTP header like the following: %%(php) header('HTTP/1.0 403 Forbidden');%% -- DarTar

Oh, and maybe 404 headers for missing pages (which would help prevent SE from spidering links to non existing pages)? -- DarTar

Ref

Coordination ticket

Change History

Changed 8 years ago by BrianKoontz

  • milestone set to 1.1.7.2

Assigned to milestone 1.1.7.2.

Changed 7 years ago by DarTar

  • description modified (diff)

adding reference to coordination ticket

Changed 6 years ago by wadmin

  • keywords acls added

Changed 4 years ago by BrianKoontz

  • milestone changed from 1.3 to 1.4
Note: See TracTickets for help on using tickets.