Re: [xSocket-develop] further proxy issues, header, cache, remove hop-by-hop headers..
Status: Inactive
Brought to you by:
grro
|
From: Timothy Schm. <tim...@we...> - 2009-02-22 16:56:49
|
Hi Gregor. > yes this is true, the method removeHopByHopHeaders() had only been > supported in eraly version of xLightweb. Can you try to explain the rational for this? > Do you use the older version > xSocket-http or xLightweb (http://xlightweb.sourceforge.net/) which > replaces xSocket-http? My classpath is set to: xlightweb-2.5.jar:xSocket-2.4.3.jar:. Without xSocket-2.4.3.jar in there, I get NoClassDefFoundError: org/xsocket/ILifeCycle. > Could you send me some links which causes 404? I would like to cross- > checks the links Sure, for instance http://www.heise.de/ gives me a 404 with 'Connection: close' on the root document. What is a bit strange is that the browser still (successfully) fetches ico, css, gif, js and other fragments. And the 404 is actually printed in the body of the browser. So the webserver is indeed aware that there is some issue. > By the way there is a experimental implementation of a HttpProxy in > the sandbox branch. See http://xlightweb.svn.sourceforge.net/viewvc/ > xlightweb/xlightweb/sandbox/HttpProxy/trunk/ Hmm, this code also doesn't seem to have any special (hop-by-hop) header treatment. (Except for setting "Via" if I'm not mistaken.) Thanks, Tim (apologies for double delivery) _______________________________________________________________________ Jetzt 1 Monat kostenlos! WEB.DE FreeDSL - Telefonanschluss + DSL für nur 17,95 EURO/mtl.!* http://dsl.web.de/?ac=OM.AD.AD008K15039B7069a |