HEAD returns 404, GET returns 200 for the same url

Bug #142576 reported by Magnus Heino
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zope 2
Invalid
Wishlist
Unassigned
Tags: bug zope
Revision history for this message
tonico (tonico) wrote :

I stumbled over this issue while checking for dead links with gURLchecker. I wonder if this has some impacts on SEO visibility.

Revision history for this message
Ian Lawrence (ianlawrence) wrote :

This still has not been fixed apparently

Tres Seaver (tseaver)
Changed in zope2:
status: New → Triaged
importance: Medium → Wishlist
Revision history for this message
Paul Dodd (paul-dodd) wrote :

This bug will increase load on the web site and traffic.

Revision history for this message
Paul Dodd (paul-dodd) wrote :
Revision history for this message
Paul Dodd (paul-dodd) wrote :

Returning 404 is correct according to http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.4
"This status code is commonly used when the server does not wish to reveal exactly why the request has been refused" but will cause extra load on the web site and traffic, thus HEAD should be supported.

Revision history for this message
Colin Watson (cjwatson) wrote :

The zope2 project on Launchpad has been archived at the request of the Zope developers (see https://answers.launchpad.net/launchpad/+question/683589 and https://answers.launchpad.net/launchpad/+question/685285). If this bug is still relevant, please refile it at https://github.com/zopefoundation/zope2.

Changed in zope2:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.