[issue8704] cgitb sends a bogus HTTP header if the app crashes before finishing headers

2022-03-15 Thread Colin 't Hart
Colin 't Hart added the comment: 1. This module is scheduled to be removed by Python 3.13 (although I preseonally am of the opinion that it is a useful module and would like to see it brought up-to-date). 2. Is reset() even necessary anymore? Can't the same results be achieved with CSS since

[issue8704] cgitb sends a bogus HTTP header if the app crashes before finishing headers

2021-03-18 Thread coyot linden
coyot linden added the comment: Ran into this also, got: AH02429: Response header name '

[issue8704] cgitb sends a bogus HTTP header if the app crashes before finishing headers

2020-09-12 Thread igs
igs added the comment: As mentioned above standard Apache does not accept the extra characters anymore and produces '500 internal error'. So the normal behaviour of this module makes things worse in most cases instead of being helpful. -- nosy: +igs _

[issue8704] cgitb sends a bogus HTTP header if the app crashes before finishing headers

2020-03-14 Thread Ryan Tu
Ryan Tu added the comment: #Maybe not a good solution I do not know the should we delete the code in cgitb.py or adjust the configration of apache httpd. My solution is deleting some code as follows: ``` return ''' --> --> --> ''' ``` Then it works very well, and it has

[issue8704] cgitb sends a bogus HTTP header if the app crashes before finishing headers

2017-05-20 Thread Артур Клесун
Артур Клесун added the comment: Apache started strict check of headers ch aracters to be valid recently. That causes it fail on "<--: spam". ``` [Sat May 20 13:09:23.056673 2017] [http:error] [pid 26379] [client 12.34.567.41:60988] AH02429: Response header name '

[issue8704] cgitb sends a bogus HTTP header if the app crashes before finishing headers

2013-07-16 Thread p0lar_bear
Changes by p0lar_bear : -- versions: +Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue8704] cgitb sends a bogus HTTP header if the app crashes before finishing headers

2013-07-16 Thread p0lar_bear
p0lar_bear added the comment: I get similar results if my CGI script sends a Content-Type header of anything besides "text/html", e.g. print('Content-Type: text/json'). -- nosy: +p0lar_bear ___ Python tracker _

[issue8704] cgitb sends a bogus HTTP header if the app crashes before finishing headers

2011-03-17 Thread Senthil Kumaran
Changes by Senthil Kumaran : -- nosy: +orsenthil ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue8704] cgitb sends a bogus HTTP header if the app crashes before finishing headers

2010-05-14 Thread Daniel Stutzbach
Daniel Stutzbach added the comment: It displays correctly in some browsers, yes, but not everything that speaks HTTP is a browser. For example, the invalid header makes C#'s WebRequest throw an exception. I hadn't noticed the 'Content-Type' on the next line of the string output by reset().

[issue8704] cgitb sends a bogus HTTP header if the app crashes before finishing headers

2010-05-14 Thread Ray.Allen
Ray.Allen added the comment: Yes, I saw the " --> --> .. So the hole page is not displayed correctly! Is there any problem with me? -- nosy: +ysj.ray ___ Python tracker ___

[issue8704] cgitb sends a bogus HTTP header if the app crashes before finishing headers

2010-05-13 Thread Dan Buch
Changes by Dan Buch : -- nosy: +meatballhat ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue8704] cgitb sends a bogus HTTP header if the app crashes before finishing headers

2010-05-13 Thread Daniel Stutzbach
Changes by Daniel Stutzbach : -- keywords: +easy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue8704] cgitb sends a bogus HTTP header if the app crashes before finishing headers

2010-05-13 Thread Daniel Stutzbach
New submission from Daniel Stutzbach : If the CGI script crashes before finishing the headers, cgitb will emit invalid HTTP headers before showing the error message. Below are HTTP headers I received, captured with a packet sniffer. Note the "<--: spam". HTTP/1.1 200 OK Date: Thu, 13 May 201