[REBOL] Re: problems with url...(and another "escaped" problem)
From: cyphre:seznam:cz at: 19-Jun-2002 9:48
Hi guys,
Thanks to all for explaining the problem...I 've thought this should be well
known problem but I haven't time for searching the bug. This list is the
best place for getting solution very quickly.
BTW I hope this bug is already reported to the RTs feedback.
Once again thanks,
Cyphre
PS: Some time ago I posted here "Generic proxy bug" problem but it seems
nonone react on this thread, maybe it was overlooked. This should be
simmilar problem but in proxy parser I think...so I repost it here:
I have noticed that I'm getting different results on web-dictionary CGI
query
while I have proxy usage on(its "generic" proxy, some version of linux's
SQUID)
here are the results:
with generic proxy usage OFF:
>> read
http://www.translator.cz/bin/translator?trn=uk2cz&gif=0&vcb=watch out
URL Parse: none none www.translator.cz none bin/
translator?trn=uk2cz&gif=0&vcb=watch out
Net-log: ["Opening" "tcp" "for" "HTTP"]
Net-log: {GET /bin/translator?trn=uk2cz&gif=0&vcb=watch out HTTP/1.0
Accept: */*
Connection: close
User-Agent: REBOL 1.2.5.3.1
Host: www.translator.cz
}
Net-log: "HTTP/1.1 200 OK"
Net-log: ["low level read of " 2048 "bytes"]
.......
and this is with generic proxy usage ON:
>> read
http://www.translator.cz/bin/translator?trn=uk2cz&gif=0&vcb=watch out
URL Parse: none none www.translator.cz none bin/
translator?trn=uk2cz&gif=0&vcb=watch out
Net-log: ["Opening" "tcp" "for" "HTTP"]
Net-log: {GET
http://www.translator.cz/bin/translator?trn=uk2cz&gif=0&vcb=watch out
HTTP/1.0
Accept: */*
Connection: close
User-Agent: REBOL 1.2.5.3.1
Host: www.translator.cz
Proxy-Authorization: Basic Og==
}
Net-log: "HTTP/1.0 200 OK"
Net-log: ["low level read of " 2048 "bytes"]
.......
Notice the escaped char difference. When proxy usage is on there are no
between "watch out". It is possible that this causing different results from
the server when the cgi string is passed to the proxy without proper
encoding?
I'm not sure if there was some thread about this...It is a new bug in proxy
parser? Or is the problem in the proxy settings?
Anyone?
