Hello, Repost because the first URL was translated by the message board. I'm extensively using the Webbrowser control and everything is almost fine... Actually I found a strange problem. I crawl to a page containing the following code: <A href=\"/event.ng/Type=click&FlightID=6121&AdID=17734&TargetID=1165&Segments=108,143,292,365,382,1035,1227&Targets=273,1165&Values=31,43,51,60,72,81,91,100,110,150,206,213,237,474,601,625,763,934,938,940,1007,1009,1046,1253,1282,1448,1907,1963,2018&RawValues=&Redirect=http:%2F%2Fwww.fnac.com%2FShelf%2Farticle.asp%3FPRID%3D1391122%26Origin%3D2003.2.10.12.24.24.0%26OriginClick%3Dyes\" target=_blank><IMG height=63 alt=\"\" src=\"http://pub.club-internet.fr/Netgravity/Fnac/100x63_massive_070203.gif\" width=100 border=0></A> When using the IHTMLAnchorElement and asking for the 'href' property, I get the following result: http://pubs.mgn.net/event.ng/Type=click&FlightID=6121&AdID=17734&TargetID=1165&Segments=108,143,292,365,382,1035,1227&Targets=273,1165&Values=31,43,51,60,72,81,91,100,110,150,206,213,237,474,601,625,763,934,938,940,1007,1009,1046,1253,1282,1448,1907,1963,2018&RawValues=&Redirect=http://www.fnac.com/Shelf/article.asp?PRID=1391122&Origin=2003.2.10.12.24.24.0&OriginClick=yes But If I issue an HTTP GET request, I get a 404 error (after redirection, the web server is a Netscape Entreprise Server). I know that if I use this URL instead (like IE does !), I will work: http://pubs.mgn.net/event.ng/Type=click&FlightID=6121&AdID=17734&TargetID=1165&Segments=108,143,292,365,382,1035,1227&Targets=273,1165&Values=31,43,51,60,72,81,91,100,110,150,206,213,237,474,601,625,763,934,938,940,1007,1009,1046,1253,1282,1448,1907,1963,2018&RawValues=&Redirect=http:%2F%2Fwww.fnac.com%2FShelf%2Farticle.asp%3FPRID%3D1391122%26Origin%3D2003.2.10.12.24.24.0%26OriginClick%3Dyes The difference is that the second URL has HTML decoded all & but kept all URL encoded characters. Using the debugger I found that because the WebBrowser control is misparsing the anchor, I also get wrong values for the 'search' property (of IHTMLAnchorElement) and so on. Is it a bug ? What can I do to deal with this problem and get a perfectly parsed URL ? Regards, R. LOPES Just programmer.