Iis6 Error Codes
Contents |
31, 20061 Share 0 0 Sigh. People are too quick to apply Harlon's Razor and assume that any "deviations" result from sc-substatus codes malicious Microsoft intent to deviate from HTTP standard, when user iis code 302 misinformation is frequently the problem… Question: I have a problem with a customer which is using IIS iis error codes list based on windows 2003. The question is simple all these deviations from the normal HTTP standard presented on IIS see following link: http://support.microsoft.com/default.aspx?scid=kb;EN-US;318380 Are they actually sent iis sc win32 status downstream to the end-user? Here is the corresponding RFC. http://www.w3.org/Protocols/HTTP/1.0/draft-ietf-http-spec.html Ideas or places to find this information? Thanks for your help.Best regards, Answer: IIS6 on Windows Server 2003 is an HTTP/1.1 Server. Your referenced RFC applies to an HTTP/1.0 Server… so it does not apply here at all. The actual HTTP/1.1 RFC which does apply
Iis Status Code 304
to IIS6 is at: http://www.w3.org/Protocols/rfc2616/rfc2616.html If you quickly browse through the official HTTP/1.1 RFC, you should see that IIS is not deviating from the normal HTTP standard at all, so there are no problems with sending custom error responses using those status codes. And even in the case of 401, 403, 404, 500, and 502, where IIS offerssub-status error codes to differentiateamongst the standard HTTP status codes,IIS is still compliant with HTTP specifications. IIS simply sends HTTP responses using the standard HTTP status code and gives you rich control of the exact content to send for the sub-stataus error. And if you use URL Custom Error to execute arbitrary code to generate the custom error response, you also control the returned HTTP status code well. For example, when IIS detects that the client IP is banned by your server's IP Restriction configuration, it triggers a 403.6 error internally, and you can configure the 403.6 custom error to generate a 403 response w
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies http://stackoverflow.com/questions/352538/setup-error-codes-on-iis-6-0 of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a error codes minute: Sign up Setup error codes on IIS 6.0 up vote 3 down vote favorite I want the IIS server to return HTTP 304 (Not Modified) when a particular file is accessed. How can I set this up? http iis share|improve this question edited Apr 14 '09 at 16:34 George Stocker♦ 39.7k25132200 asked Dec 9 '08 at 12:01 Sesh 3,73921735 add a due to server comment| 2 Answers 2 active oldest votes up vote 1 down vote accepted Check the "Enable Content Expiration" box on the HTTP Headers tab in IIS Manager: IIS 6.0 F1: Web Site Properties - HTTP Headers Tab share|improve this answer answered Dec 10 '08 at 4:51 Christopher G. Lewis 4,0231333 add a comment| up vote 1 down vote AFAIK, it isn't possible to do this (in IIS). There are a few criteria that have to be met for this code to be sent out: Client must have cached copy of page. The request's If-Modified-Since HTTP Header Time/date stamp must match what's on the server. If both of those conditions are true, the server will return a HTTP 304 status code. share|improve this answer answered Dec 9 '08 at 12:53 George Stocker♦ 39.7k25132200 How would you check to see if this feature is activated? Does it need to be activated, or is it just ON by default? –Diodeus Dec 15 '08 at 19:30 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google