>Number: 4224 >Category: mod_browser >Synopsis: I get an inconsistend error, incomplete header sent error, but >it works fine with ALL other browsers >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Sat Apr 10 09:40:01 PDT 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.1.1 - 1.3.6 >Environment: There is no problem compiling, Using FreeBSD 3.0 in this case but I have the same problem on all of my servers. I also have it with apache 1.1.1 ... any only with MSIE 5.0 >Description: I upgraded my apache, did everything I can think of, still have same problem. I run a chat site which uses a C based CGI to repost the data which is sent to the chat server on a socket.
MSIE 5.0 will run fine for awhile then I get the incomplete header error. I put MSIE 5\.0; BrowserMatch line in to give HTTP-1.0 responses but this didnt' fix it either. I can backpage twice and get it to run again, but the problem gets more frequent as I "chat" more. http://www.alamak.com/login.html is the USA site login. Could you put in a section to the broswer compliance section for MSIE 5.0? And if you have any clue as to how to fix this I'd be very appreciative. If I can't fix it and it's MickySucks problem then let me know so I can forget about it and put the blame on them. *laugh* UR favorite unix bigot .. John >How-To-Repeat: Go to http://www.alamak.com/login.html and login to the chat Chat with MSIE 5.0 for about 5 minutes and you'll get an error. The error log says it's incomplete header information. >Fix: Nope, tried everything I can think of... icnluding installing the latest apache. >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]
