IIS response status 302 then 200 for same URL - iis-7.5

What causes IIS 7.5 to send response 302 and then immediately response 200 for the same page URL request. IE11 F12 Developer Tool Debugger 302 message.
Condition began when IIS web server was upgraded from IIS6 to IIS7.5. Server log shows the 2 statuses occurring at the same date time second. Server error occurs for all page request types (HTML, ASP, etc.).

Related

why http 307 internal redirect workig only on Chrome and not firefox?

So I have an API endpoint to which CORS requests sent over http are redirected with the http 308 permanent redirect in the response. In Firefox, the response is as expected, a 308 status code with the upgraded https location header to which Firefox outright rejects and refuse to redirect/upgrade to https. In Chrome however, the response from the API with the header Non-Authoritative-Reason: HSTS is set, to which Chrome performs 307 an internal redirect. I understand why Chrome(cause of HSTS) does this, but how is this behavior isn't implemented in Firefox. In Firefox, the browser just rejects the CORS response despite the 308 redirect URL, while Chrome fakes a request and then upgrades automatically to the https version of the URL.

Prevent upgrading request to https

I am trying to make an XHR request to my dev server over http and the request gets blocked on Chrome or gets upgraded to https on Firefox which then never resolves. Is there a way to allow insecure requests on my site? The site too is insecure and the static html is served fine but the XHR gets blocked. It's not actually "mixed content" but Chrome treats it as such and blokcks the request.
The dev server is not served over https but the production server will be.

Custom 404 error page for stopped websites on IIS

When you stop a website on IIS and you try to surf to the binded URL, you get a general 404 error page. As one would expect.
But is there a way to edit this page/or set a custom page?
As far as I know, if you stop the site, that means the IIS will not listen the IIS site's port.
So the request will not send to the IIS, IIS will not return any response to the client. The server refused the connection.
In my opinion, there is no way to set the a custom page by IIS.

IIS 7.5 HTTP Error 404

Error Summary
HTTP Error 404.0 - Not Found
The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.
Detailed Error Information
Module IIS Web Core
Notification MapRequestHandler
Handler ASPClassic
Error Code 0x80070002
What could be the possible cause for this error? I've been cracking what could be wrong. I have set up my websites and IIS7.
When you try to access content on a server that is running Internet Information Services (IIS) 7.0, 7.5, or 8.0 by using the HTTP protocol, IIS returns a numeric code that indicates the status of the response. The HTTP status code is recorded in the IIS log. Additionally, the HTTP status code may be displayed in the client browser.
4xx - Client error :
These HTTP status codes indicate that an error occurred and that the client browser appears to be at fault. For example, the client browser may have requested a page that does not exist. Or, the client browser may not have provided valid authentication information.
The classic version of ASP is not installed by default. Because of this, you might see HTTP 404 errors when you try to browse to an ASP page on your server, or you might see the source code for your ASP page displayed in your browser window.
Both of these error conditions are created when configuration settings
that are used to define the environment for classic ASP are not
installed.
Steps to install are listed here
Edit 1 :
Check the application pool and applications associated.
Could you be restricted because of your request size limit?
You'll get a 404.0 if your request size goes beyond the limit you've set in the web.config
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="4000000000" />
</requestFiltering>
</security>

IIS 7.5 returning 500 error on first request (application starts/recycles)

I'm hosting a simple html file in IIS 7.5 on Windows Server 2008R2. I've assigned the site a default application pool with No Managed Code. There is nothing more in the folder other than the index.html file and a css file and I haven't changed any other setting within IIS.
On the first request and after every site restart of the site a 500 Internal Error is returned. The following error in the HTTPERR log seems to be the cause:
2014-07-04 etc .......- - - - - Timer_ConnectionIdle -
On subsequent requests the page loads fine, no problems. Why is this error being thrown on first request and how can I fix this? It doesn't seem to be related to the application pool as it doesn't happen when I recycle it, only when I stop and restart the site.

Resources