>Is there another more prefered way of finding out what the browser is sending to the server, for future reference? Internet Explorer: iehttpheaders http://www.blunck.info/iehttpheaders.html Firefox: Tamper Data https://addons.mozilla.org/extensions/moreinfo.php?id=966 or Livehttpheaders http://livehttpheaders.mozdev.org/ All Tools give you the whole bunch of headers which the browser gets and sends. Tamper Data has a plus. With this tool you can change the value of a header before the browser will send it back to server with the next request. Cool! Greetings Oliver -----Ursprüngliche Nachricht----- Von: David Salisbury [mailto:salisbury@xxxxxxxxx] Gesendet: Di 10.01.2006 19:06 An: users@xxxxxxxxxxxxxxxx Betreff: Re: [users@httpd] 2.2 Troubles ----- Original Message ----- From: "Joshua Slive" <joshua@xxxxxxxx> > On 1/9/06, David Salisbury <salisbury@xxxxxxxxx> wrote: >> >> Is anyone else out there having trouble with 2.2.0? For me, I only get a blank page for our home page. This happens >> in I.E. and firefox, though sometimes in one and not the other. The header communication seems to be: >> >> GET / HTTP/1.1 >> Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, application/vnd.ms-excel, >> application/vnd.ms-powerpoint, application/msword, */* >> Accept-Language: en-us >> Range: bytes=0- >> Unless-Modified-Since: Tue, 05 Jul 2005 23:13:46 GMT >> If-Range: "9b5f95-1e30-3c6dde80" >> User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; InfoPath.1; .NET CLR 2.0.50727) >> Host: preview >> Proxy-Connection: Keep-Alive > > That's a very weird request. Unless-Modified-Since? Range: bytes=0-? > Is that really a standard browser with no proxy in the path? > > In general when there are no-content problems, the first thing to try is > EnableSendfile Off > So you should try that. But there is definintely something weird > going on with byteranges in your case. > > Joshua. Whaooooooo... That works!!! Thank you! I suppose using this directive means things aren't as efficient as they could be, but then, that's nothing new here. :) I don't understand the weird requests of the headers either. Maybe we have some weird browser-used libraries installed. I was using Achilles in between the browser and server to capture the headers, but it is not suppose to modify the communication unless you edit things manually. Is there another more prefered way of finding out what the browser is sending to the server, for future reference? Thanks! -Dave --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
<<winmail.dat>>
--------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|