I cannot get an escaped URL like the following to work with pound:
http://dev-svbronze.pippiandcarlos.com/productDetail%3FproductName%3DMushroom%20knob%26imageUrl%3Dknobs/k_201.jpg In the log I get this message: Nov 13 01:08:49 sphinktop pound: (b7a66b90) e500 can't read header Nov 13 01:08:49 sphinktop pound: (b7a66b90) e500 response error read from 127.0.0.1:3007/GET /productDetail%3FproductName%3DMushroom%20knob%26imageUrl%3Dknobs/k_201.jpg HTTP/1.1: Success (0.004 secs) Here is a packet trace: GET /productDetail%3FproductName%3DMushroom%20knob%26imageUrl%3Dknobs/k_201.jpg HTTP/1.1 Host: dev-svbronze.pippiandcarlos.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.17) Gecko/20080928 SeaMonkey/1.1.12 Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive Referer: http://dev-svbronze.pippiandcarlos.com/collections?pages=Knobs Cookie: SESSIONID=D74870F6FE795D02D308ED81533DEEFA HTTP/1.0 500 Internal Server Error Content-Type: text/html Content-Length: 58 Expires: now Pragma: no-cache Cache-control: no-cache,no-store An internal server error occurred. Please try again later.HTTP/1.0 500 Internal Server Error Content-Type: text/html Content-Length: 58 Expires: now Pragma: no-cache Cache-control: no-cache,no-store An internal server error occurred. Please try again later. If I use an unescaped URL, it works (but I cannot use an unescaped URL because I need to encode "/" characters in the real world): http://dev-svbronze.pippiandcarlos.com/productDetail?productName=hi_there&imageUrl=some_image.jpg If I bypass pound by designating the backend server port in the URL, it works: http://dev-svbronze.pippiandcarlos.com:3007/productDetail%3FproductName%3DMushroom%20knob%26imageUrl%3Dknobs/k_201.jpg I believe the backend server is serving the page, but pound is rejecting it during the response phase. Which seems odd because the URL has made it through pound by that point. Maybe there is a header in the response that pound doesn't like. I would bet that the header contains the original URL, or some part of it, and pound complains if it has escape sequences in it. I cannot see it in my packet trace. I know that the backend server is processing the page because I have some debugging messages server-side that are getting output into the console. This happens even when pound is in the picture. Is this a known issue? Is there a fix/workaround/configuration? Carlos Konstanski -- To unsubscribe send an email with subject unsubscribe to [EMAIL PROTECTED] Please contact [EMAIL PROTECTED] for questions.
