Lewis, That is correct , that is the only discrepancy that I have noticed so far , I think whats happening here is that any23 is encoding an already encoded URL , I have not found a way to avoid that in Java i.e avoid encoding an already encoded URL. Is there a way to do so ? Does any23 consider the possibility of the URL being already encoded ?
Thanks. On Wed, Oct 2, 2013 at 8:39 PM, Lewis John Mcgibbney < [email protected]> wrote: > Hi, > > On Sun, Sep 29, 2013 at 6:44 PM, <[email protected]>wrote: > >> >> I seem to be running into issues where the URL that is submitted to Any23 >> is being encoded in a format that is causing the URL to become invalid , I >> am not sure if the URL that is being encoded was already encoded by Any23 >> or if Any23 just encoded the URL in a wrong format. >> > > From what I can see below the 2nd (encoded) URL includes hash # as the > only difference. Is this correct? Are there any other discrepancies which > you've noticed. > I checked out Jira instance and nothing like this has been reported before. > Thanks > Lewis > > >> >> Please see the example below and advise. >> >> URL (submitted to Any23 i.e before encoding happens) : >> >> >> http://www.xxx.com/site/searchpage.jsp?_dyncharset=ISO-8859-1&id=pcat17071&type=page&ks=960&st=Just_Dance_Disney_Party_67055&sc=Global&cp=1&sp=&qp=crootcategoryid%23%23-1%23%23-1~~q4a7573745f44616e63655f4469736e65795f50617274795f3637303535~~ncabcat0700000%23%231%23%231&list=y&usc=All+Categories&nrp=15&iht=n >> >> URL After Encoding ( I know this by printing the URL from >> DefaultHttpCleint.java): >> >> >> http://www.xxx.com/site/searchpage.jsp?_dyncharset=ISO-8859-1&id=pcat17071&type=page&ks=960&st=Just_Dance_Disney_Party_67055&sc=Global&cp=1&sp=&qp=crootcategoryid#%23-1%23%23-1~~q4a7573745f44616e63655f4469736e65795f50617274795f3637303535~~ncabcat0700000%23%231%23%231&list=y&usc=All%20Categories&nrp=15&iht=n >> >> >> > > > -- > *Lewis* >
