To clear things up. For HTTP proxy, I'm using 1.1 specification in both 1.3.2 and 1.3.3. If pRSSreader goes directly to he web it sends: GET / HTTP/1.1 Host: <hostname> If it goes via proxy, it send: GET <full_url> HTTP/1.1 Host: <hostname> the <full_url> was neccesary in 1.0 (AFAIK). I was debuging that with squid (http proxy). Both version should use the same format. Sorry for previous confusions. Thomas M. Hofmann wrote: > Hi again, > > I thought you were using HTTP 1.1 only because on the preference page > where you can override the proxy settings from connection manager you > can only select HTTP 1.1. > > Anyway I understand that it is not easy to find the problem from your > side. I already wanted to intercept the traffic using a local proxy on > my desktop but had troubles with the connection over Active Sync. The > idea was to compare the requests made by 1.3.3 with the one from 1.3.2. > There must be a difference in the HTTP request.=20 Please do so and report the results. Perhaps we will figure out what is going on here. -- David > > I will let you know when I achieved this. > > Thomas=20 > > -----Original Message----- > From: prssr-devel-ml-bounce@xxxxxxxxxxxxx > [mailto:prssr-devel-ml-bounce@xxxxxxxxxxxxx] On Behalf Of David Andrs > Sent: Donnerstag, 25. Januar 2007 5:50 > To: prssr-devel-ml@xxxxxxxxxxxxx > Subject: [prssr-devel-ml] Re: 1.3.3 beta 4 > > I'd like to help you with this, but you understand that it is very hard, > becuase I'm not able to emulate your environment on my device to debug > it. > > For 1.3.3, I have added https support, but it still has some limitations > with proxies. > > The rest of HTTP implementation should be the same. I made some fixes, > but they were extending not restricting ones. > > Thomas M. Hofmann wrote: >> Hi again, >> =20 >> Maybe this has to do with HTTP 1.1 and maybe the proxy only supports >> 1.0. I am guessing this because of the HTTP error code 400 I get with >> 1.3.3. >> =20 >> Did this change? Did 1.3.2 use HTTP 1.0? > I do not thing so, but not completely sure about it. HTTP 1.0 is used if > you are using HTTP proxy, but 1.3.3 uses also HTTP 1.0. So, no changes > here. > > -- > David > >> =20 >> What else change in HTTP protocol that could lead to the error 400? >> =20 >> Thomas=3D20 >> =20 >> -----Original Message----- >> From: prssr-devel-ml-bounce@xxxxxxxxxxxxx >> [mailto:prssr-devel-ml-bounce@xxxxxxxxxxxxx] On Behalf Of Thomas M. >> Hofmann >> Sent: Montag, 22. Januar 2007 9:10 >> To: prssr-devel-ml@xxxxxxxxxxxxx >> Subject: [prssr-devel-ml] Re: 1.3.3 beta 4 >> =20 >> Hi David, >> =20 >> I checked for typos. Unfortunately I did not export the registry > before >> I uninstalled 1.3.2. >> =20 >> When I uninstalled 1.3.2 I left the cache data untouched and then I >> installed the 1.3.3 beta4 into the same location. >> =20 >> Another thing that I noticed is that with 1.3.2 I would sometimes need >> to close pRSS and then start Pocket IE, load a page and then restart >> pRSS to get it to connect successfully. >> =20 >> I saw a similar problem back in autum 2006 on this list but now answer >> as far as I remember. >> =20 >> So if nothing regarding the Additonal HTTP Headers has do you have > some >> advice on how I can get more info about this is not working anymore. I >> get Error 400 which I do not remember getting before. >> =20 >> Thanks >> =20 >> -----Original Message----- >> From: prssr-devel-ml-bounce@xxxxxxxxxxxxx >> [mailto:prssr-devel-ml-bounce@xxxxxxxxxxxxx] On Behalf Of David Andrs >> Sent: Montag, 22. Januar 2007 6:46 >> To: prssr-devel-ml@xxxxxxxxxxxxx >> Subject: [prssr-devel-ml] Re: 1.3.3 beta 4 >> =20 >> No changes regarding this. Maybe some typo in additional HTTP headers > or >> user agent string? >> =20 >> Moreover, have you uninstall 1.3.2 before installing 1.3.3? If not, > you >> will need to uninstall 1.3.3, may be you will have to do manual clean >> and then do the clean install. >> =20 >> -- >> David >> =20 >> Thomas M. Hofmann wrote: >>> Hi, >>> =3D3D20 >>> Today I installed 1.3.3 beta 4 coming from 1.3.2. I am trying to use >> the >>> O2 WAP falt with pRSS and got everything working with 1.3.2. I had >>> changed the User Agent string to match my pocket ie and I also added >> the >>> "Addtional HTTP Headers" registry key. >>> =3D3D20 >>> Now, that I installed 1.3.3 beta4 and recreated the registry settings >> I >>> get HTTP error 400 all the time when I try to update my news =3D3D >> feeds.=3D3D3D20 >>> =3D3D20 >>> Are there any changes regarding this? >>> =3D3D20 >>> Thank you. >>> =3D3D20 >>> Thomas >>> -- >>> pRSSreader development mailing list >>> prssr-devel-ml@xxxxxxxxxxxxx >>> //www.freelists.org/archives/prssr-devel-ml >>> =3D3D20 >>> =3D3D20 >>> =3D3D20 >> -- >> pRSSreader development mailing list >> prssr-devel-ml@xxxxxxxxxxxxx >> //www.freelists.org/archives/prssr-devel-ml >> =20 >> =20 >> =20 >> -- >> pRSSreader development mailing list >> prssr-devel-ml@xxxxxxxxxxxxx >> //www.freelists.org/archives/prssr-devel-ml >> =20 >> =20 >> =20 >> -- >> pRSSreader development mailing list >> prssr-devel-ml@xxxxxxxxxxxxx >> //www.freelists.org/archives/prssr-devel-ml >> =20 >> =20 >> =20 > -- > pRSSreader development mailing list > prssr-devel-ml@xxxxxxxxxxxxx > //www.freelists.org/archives/prssr-devel-ml > > > > -- > pRSSreader development mailing list > prssr-devel-ml@xxxxxxxxxxxxx > //www.freelists.org/archives/prssr-devel-ml > > > -- pRSSreader development mailing list prssr-devel-ml@xxxxxxxxxxxxx //www.freelists.org/archives/prssr-devel-ml