Re: HTTP 403 served as text/plain
Greg Ames says: >Jerry Baker wrote: >> >> Using the current CVS, Apache 2.0.40-dev is sending HTTP 403 messages as >> text/plain. >> >> When I set up a deny from [my ip], I get a plain text message that looks >> like this: >> >> >> >> 403 Forbidden > >yeah, we have hacks on top of hacks in ap_send_error_response and functions it >calls, resulting in content-type being set in the wrong request_req sometimes >when we put out canned error messages. I tried cleaning up some of the hacks a >while back, but it was more complex than I thought. I suppose we could just >focus on getting the content-type and other related fields set in the correct >request_req and make it look prettier at the browser. > >Greg > > > Incidentally, it was fixed at some point after this email, and before 07-16.
Re: HTTP 403 served as text/plain
Jerry Baker wrote: > > Using the current CVS, Apache 2.0.40-dev is sending HTTP 403 messages as > text/plain. > > When I set up a deny from [my ip], I get a plain text message that looks > like this: > > > > 403 Forbidden yeah, we have hacks on top of hacks in ap_send_error_response and functions it calls, resulting in content-type being set in the wrong request_req sometimes when we put out canned error messages. I tried cleaning up some of the hacks a while back, but it was more complex than I thought. I suppose we could just focus on getting the content-type and other related fields set in the correct request_req and make it look prettier at the browser. Greg
HTTP 403 served as text/plain
Using the current CVS, Apache 2.0.40-dev is sending HTTP 403 messages as text/plain. When I set up a deny from [my ip], I get a plain text message that looks like this: 403 Forbidden Forbidden You don't have permission to access /mozilla/voting/Berkjg;ljfg on this server. Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. Apache/2.0.40-dev Server at jerbaker.dhs.org Port 80
