"No handler matched ..." results in 502 - Bad Gateway

[markus]

When installing the latest trunk on IIS 6 without fixing IIS' path_info behaviour you'll get a 502 - Bad Gateway error.

This is because Trac reports "No handler matched request to …" without setting any Content-Type (should be text/plain in this case). In consequence, the webserver (IIS in my case) complains about the missing set of HTTP headers.

[Jonas Borgström]

Trac trunk sets the Content-Type header correctly. Here's the full list of headers generated by the "No handler matched" 404 page:

Server: tracd/0.10dev Python/2.4.3
Date: Sun, 11 Jun 2006 19:56:07 GMT
Cache-Control: must-revalidate
Expires: Fri, 01 Jan 1999 00:00:00 GMT
Content-Type: text/plain;charset=utf-8
Content-Length: 323

I'm closing this ticket, please reopen it if this still is an issue.

[markus]

Let me guess, you tried to access an address like ​http://projects.edgewall.com/trac/foo and recorded the headers listed above, right?

[markus]

For the record: Fixed by Christian in [3369].

[Christian Boos]

Thanks for the info, I didn't realize that this would fix this particular issue. Good news, then!

[Christian Boos]

(clearing report:35)