Is it just me or is it IIS? (redirects)

[rrsub]

IIS (5.0 in this case) has a redirect feature under the Home Directory tab of a web site.

I've tried this on multiple servers / many web sites to test this but every single redirect produces errors.

Web site for

http://www.site1.com.

Under Home Directory select:
-redirection to a URL
-Redirect to:

http://www.site2.com

-permanent redirecton for this resource

Under the protocol, the server header should produce a HTTP/1.1 301 Moved Permanently.
The receiving site (

http://www.site2.com)

gets a 302 Found


Instead, it produces
HTTP/1.1 301 Error

The client still redirects without any errors on the browser but the logging is screwed up as well as any bot traffic.

Service Pack 2 and 3 have this. Not sure if OOB and SP1 do but I don't see why it would have changed.

 

[browolf]

googling it seems a lot of http error lists, list 301 as "Error (Moved Permanently)"
e.g.

http://www.kortenhorst.com/tools/web_status_codes.php#301

and webpages too say
"301 Error: Page Moved Permanently!"

http://trainweb.com/railpix/

It not clear why this is but it seems normal.

w3.org says
"The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the Request-URI to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise.

The new permanent URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).

If the 301 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.

Note: When automatically redirecting a POST request after
receiving a 301 status code, some existing HTTP/1.0 user agents
will erroneously change it into a GET request."

what this means in practice, I dont know.

===============
Security Forums

http://www.security-forums.com

 

[rrsub]

The way I understand the RFC's is that 400 are client errors, 500 are server errors. 301 error is a fallacy with IIS.

301 should be Moved Permanently not
301 (error) Moved Permanently. This totaly screws any indexing.

 

[browolf]

we can only assume that IIS isnt following the RFC as closely as it could/should.


===============
Security Forums

http://www.security-forums.com