05-16-2007, 10:59 AM
|
|
Senior Member
|
|
Join Date: May 2007
Posts: 237
|
|
Response via litespeed:
Code:
05/16/07 13:53:04 Browsing http://example.net/blahblah123
Fetching http://example.net/blahblah123 ...
GET /blahblah123 HTTP/1.1
Host: example.net
Connection: close
User-Agent: Mozilla/5.0 (WinNT)
HTTP/1.1 404 Not Found
Date: Wed, 16 May 2007 17:53:08 GMT
Server: LiteSpeed
Connection: close
Content-Length: 8
Content-Type: text/html
response via apache:
Code:
05/16/07 13:57:03 Browsing
http://example.net/blahblah123
Fetching http://example.net/blahblah123 ...
GET /blahblah123 HTTP/1.1
Host: example.net
Connection: close
User-Agent: Mozilla/5.0 (WinNT)
HTTP/1.1 404 Not Found
Date: Wed, 16 May 2007 17:57:03 GMT
Server: Apache
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=iso-8859-1
8
missing"
0
By the way, I have no idea what that 8 and 0 is before and after the apache ErrorDocument text is.
Is it part of the "chunked encoded" process where it's a segment of sorts?
Ah it might be the content-length for that segment of the chunked output.
Apparently I also accidentally left an end quote on the the "missing" when it should be just "missing - but I doubt that is what is messing up lsws right?
So is apache getting around the issue by using chunked output.
I notice apache also appends a charset, though nothing is specified in my htaccess, must be in httpd or some kind of default. Is it not important for litespeed to mimic that behavior? Will litespeed obey if I add this to htaccess?
AddDefaultCharset iso-8859-1
Last edited by aww; 05-16-2007 at 11:16 AM..
|