Do you mean bug 19954? http://issues.apache.org/bugzilla/show_bug.cgi?id=19954 This has been already resolved in the current 2.2 version. I debugged a little today and I found out it is not about cache. hts blocks in read() when it wants to read the POST request from Apache. Here is the detail, "hts" first gets a GET request from Apache where the src port is N. it reads the request and returns a response. Then it gets the POST request from Apache where the src port is M, when it wants to read the content of the reqeust, it blocks. Can this issue be resolved in some way? On 6/2/07, Staf Wagemakers <staf.wagemakers@xxxxxxxxx> wrote:
On 6/1/07, Jiajin Yu <zeroyjj@xxxxxxxxx> wrote: > > Have anyone successfully configured httptunnel with Apache2.2? I use > simple configuration just like this: > > ProxyRequests Off > > <Proxy *> > Order deny,allow > Allow from all > </Proxy> > > ProxyPass /foo http://localhost:8888 > ProxyPassReverse /foo http://localhost:8888 > > When I start htc and hts in my machine, from the debugging message, it > seems that htc sends a POST request first, then a GET. But hts always > first receives GET request from mod_proxy of Apache. I modify the > code so that htc will sleep for 2 seconds after it sends out POST > request, but hts still receives GET first. From the access.log, it > also seems that mod_proxy caches POST even though the POST is earlier > than GET because the log of POST is written after GET. Can anyone give > me some hints or solution? Thanks. I've played with http_tunnel a few years ago. If I remember it correctly there was problem with mod_proxy and GNU httptunnel and I needed to apply a patch to get it working. I don't remember the patch id perhaps google can help. regards, -- Staf Wagemakers - http://www.wagemakers.be
-- Regards, Jiajin --------------------------------------------------------------------- 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
|