On 17/12/2009, at 00:06, Antonio Pérez wrote:
> On Wed, Dec 16, 2009 at 9:16 PM, Alvaro Lopez Ortega
> <[email protected]> wrote:
>> On 15/12/2009, at 22:02, Alvaro Lopez Ortega wrote:
>>> On 15/12/2009, at 20:22, Yo'av Moshe wrote:
>>> 
>>>> I opened a topic about this issue long ago, but it was not resolved, and 
>>>> all my last messages got no reply... I usually understand this as "sorry, 
>>>> can't help ya", but I thought I'd give it another last chance because 
>>>> maybe you've missed it since the topic started pretty long ago (Aug' 09).
>>>> So, sorry for the double posting, this is last time I'm bringing up this 
>>>> to the ML.
>>> 
>>> Last time I tried, I did not manage to reproduce the problem. You're right 
>>> though, I should have replied to your mail.  Anyway, I'll give it another 
>>> try tomorrow and I'll let you know.
>> 
>> As you know each header entry should end by the \r\n (CR LF) set. 
>> Alternatively, it could end by a single \n (LF) character.  However, if you 
>> take a look at this header snipped you'll see how your application is 
>> prepending an additional \r character:
>> 
>> =========
>> Set-Cookie: noal-visit=66e3682d0e27823bb1c57de8a912ed0dd71245c3; Path=/\r\r\n
>> =========
>> 
>> When Cherokee detects that malformed header entry, it aborts the request. 
>> And therefore, it replies a "502 Bad gateway" error.  As soon as you fix the 
>> back-end, everything should start working just fine.
> 
> I don't get the additional \r character:
> 
> =========
> $ curl -I http://maagal.dontexist.org:40/ | hd
>  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
>                                 Dload  Upload   Total   Spent    Left  Speed
>  0  5882    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0
> 00000000  48 54 54 50 2f 31 2e 31  20 32 30 30 20 4f 4b 0d  |HTTP/1.1 200 OK.|
> 00000010  0a 44 61 74 65 3a 20 54  68 75 2c 20 31 37 20 44  |.Date: Thu, 17 D|
> 00000020  65 63 20 32 30 30 39 20  30 31 3a 35 35 3a 31 39  |ec 2009 01:55:19|
> 00000030  20 47 4d 54 0d 0a 53 65  72 76 65 72 3a 20 43 68  | GMT..Server: Ch|
> 00000040  65 72 72 79 50 79 2f 32  2e 33 2e 30 0d 0a 43 6f  |erryPy/2.3.0..Co|
> 00000050  6e 74 65 6e 74 2d 4c 65  6e 67 74 68 3a 20 35 38  |ntent-Length: 58|
> 00000060  38 32 0d 0a 43 6f 6e 74  65 6e 74 2d 54 79 70 65  |82..Content-Type|
> 00000070  3a 20 74 65 78 74 2f 68  74 6d 6c 3b 20 63 68 61  |: text/html; cha|
> 00000080  72 73 65 74 3d 75 74 66  2d 38 0d 0a 53 65 74 2d  |rset=utf-8..Set-|
> 00000090  43 6f 6f 6b 69 65 3a 20  6e 6f 61 6c 2d 76 69 73  |Cookie: noal-vis|
> 000000a0  69 74 3d 65 65 65 66 66  38 33 35 39 63 36 31 36  |it=eeeff8359c616|
> 000000b0  34 39 32 32 65 37 30 62  31 34 61 37 63 66 30 31  |4922e70b14a7cf01|
> 000000c0  35 62 32 35 63 61 66 64  38 32 63 3b 20 50 61 74  |5b25cafd82c; Pat|
> 000000d0  68 3d 2f 0d 0a 43 6f 6e  6e 65 63 74 69 6f 6e 3a  |h=/..Connection:|
> 000000e0  20 63 6c 6f 73 65 0d 0a  0d 0a                    | close....|
> =========
> 
> Unless Yo'av has solved the problem... :)

I couldn't tell you, maagal.dontexist.org:40 seems to be down now.

Anyway, I've a half-cooked patch that allows to set the proxy in a more 
permissive mode. Let's see how it goes once the patch is applied.

--
Octality
http://www.octality.com/

_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee

Reply via email to