Re: [twsocket] HTTP client relocation

2005-11-20 Thread Maurizio Lotauro
On 20-Nov-05 11:04:30 Francois PIETTE wrote: >The question is: Should the HTTP client component implement this >relative >path removal algorithm ? If it is formally valid yes. But it could be tricky to do because sometimes the relative path could be a little "strange" :-

Re: [twsocket] HTTP client relocation

2005-11-20 Thread Francois PIETTE
The question is: Should the HTTP client component implement this relative path removal algorithm ? >>> >>> If it is formally valid yes. But it could be tricky to do because >>> sometimes the relative path could be a little "strange" :-) > >>Can you give and example of "strange" relativ

Re: [twsocket] HTTP client relocation

2005-11-19 Thread Maurizio Lotauro
On 19-Nov-05 09:59:28 Francois PIETTE wrote: >>>The question is: Should the HTTP client component implement this relative >>>path removal algorithm ? >> >> If it is formally valid yes. But it could be tricky to do because >> sometimes the relative path could be a little "strange" :-) >Can you giv

Re: [twsocket] HTTP client relocation

2005-11-19 Thread Angus Robertson - Magenta Systems Ltd
> We could add a new property LocationChangeMaxCount with a default > value of let's say 5 (as suggested by RFC1945 section 9.3) and an new > event OnLocationChangeExceeded taking as arguments the sender, the > current count (RelocationCount), and as a var argument, defaulting to > FALSE, a boo

Re: [twsocket] HTTP client relocation

2005-11-19 Thread Francois PIETTE
>>The question is: Should the HTTP client component implement this relative >>path removal algorithm ? > > If it is formally valid yes. But it could be tricky to do because > sometimes the relative path could be a little "strange" :-) Can you give and example of "strange" relative path ? -- Con

Re: [twsocket] HTTP client relocation

2005-11-19 Thread Francois PIETTE
>> But there is another problem in relocation when the relocation is to the >> same URL, and the component gets stuck in a loop. This frequently happend because many relocations are just to grab cookies. If the application doesn't handle cookies, you end with an infinite loop. > This is an easy

Re: [twsocket] HTTP client relocation

2005-11-18 Thread Nicholas Sherlock
Angus Robertson - Magenta Systems Ltd wrote: >But there is another problem in relocation when the relocation is to the same >URL, and the component gets stuck in a loop. > This is an easy fix, just set a relocation limit, like Internet Explorer and Firefox do Cheers, Nicholas Sherlock -- To

Re: [twsocket] HTTP client relocation

2005-11-18 Thread Maurizio Lotauro
On 17-Nov-05 20:00:16 Francois PIETTE wrote: >The question is: Should the HTTP client component implement this relative >path removal algorithm ? If it is formally valid yes. But it could be tricky to do because sometimes the relative path could be a little "strange" :-) And the problem that Ang

Re: [twsocket] HTTP client relocation

2005-11-17 Thread Angus Robertson - Magenta Systems Ltd
> The question is: Should the HTTP client component implement this > relative path removal algorithm ? In my opinion it should. I've not reported it before, and I've lost my fix due to installing new ICS versions over the last month. But there is another problem in relocation when the reloc

[twsocket] HTTP client relocation

2005-11-17 Thread Francois PIETTE
When using the url "http://mediaphor.louis.info/de/";, the HTTP client component hit a 404 error after a relocation. The problem is that the relocation is done to "../" so the component send the request "GET /de/../" and the server doesn't like it. In my opinion, it is a problem at server side.