This project is read-only.

404 page response not always being sent to browsers

Topics: Core, Troubleshooting
Apr 2, 2014 at 10:13 PM
We've run into a really strange problem with Orchard and we've been trying (and failing) to solve it for over a week now. Whenever we request a URL that doesn't map to anything on the site we're building, the NotFound shape gets properly built and the page completely rendered within Orchard, but only rarely actually gets sent to the browser.

I've followed along in the debugger, and observed the traffic in Fiddler2, so I know that the page HTML is being fully and properly constructed, and that the HTML content isn't always sent along. When it's missing, there's a Content-Length: 0 header as well.

Anyone have an idea of what might be going on? Is it IIS? Is it ASP.NET? Is it Orchard itself? And is there some way with 1.7.x to at least force 404 errors to a static page as a workaround in the meantime?
Apr 3, 2014 at 12:18 AM
Some further investigation has demonstrated that so long as a valid .ASPXAUTH cookie is sent with the request, the content for the 404 page gets sent to the browser. However, without that cookie (or with an invalid one), we get Content-Length: 0 and no page content.