Hello,
\nI have built an Android application that uses extensive use of\nHttpClient to contact a remote server. The application is stable\nand I haven't changed any of the networking code in quite a\nwhile.
\nI'm eager to use the new Android features in the 1.5 SDK. After\nupgrading to the 1.5 SDK my application can no longer talk to the\nclient using HttpClient.
\nThe remote server is Tomcat. Because of ticket #968, I can't\nrely on the jsessionid cookie to be properly utilized by\nHttpClient, so to get around it, I append the jsessionid to the end\nof the URL as necessary. Something this:
\n/someurl.action;jsessionid=123456
\nThis all worked correctly and without fail until I upgraded to\nthe 1.5 SDK. Now, when the jsessionid is appended to the URL,\nTomcat throws a 404 error with this in the error message:
\nThe requested resource\n(/mwf/mobile/home/Home.action%3Bjsessionid%3D9498648CA1E54C6743AA5723276EBF51)\nis not available.
\nYou can see in the error message that the semicolon before\njsessionid was URL encoded, as was the equals sign after\njsessionid. I don't know for sure, but I assume that pre 1.5 these\ncharacters were NOT encoded.
\nThis is a show stopper bug for me. Due to ticket #968 I can't\nrely on the jsessionid cookie, and the work around of appending\njsessionid to the URL is now failing too. My app effectively cannot\ncontact the server since the session ID cannot be passed along.\nMaybe Tomcat is pickier than other servers, but I can't just up and\nchange servers especially when it worked before.
\nCould you please investigate?
\nThank you and keep up the great work on Appcelerator\nTitanium!!!
\n-Ryan
For QA, a simple app.js:
\n\nvar xhr = Ti.Network.createHTTPClient();\nxhr.autoEncodeUrl = false;\nxhr.open('GET','http://www.appcelerator.com/x/y/z;jsessionid=ABCD');\nif (xhr.location.indexOf(';jsession')<0) {\n alert('FAIL. Cannot find \";jsessionid\" in location url: ' + xhr.location);\n} else {\n alert('SUCCESS. Found \";jsessionid\" in location url: ' + xhr.location);\n}\n(from [bcdf46569b53be86fc029577ec5147abda6a6c17])\n[#2589 state:fixed-in-qa][#1491] Add\nautoEncodeUrl property to HTTPClient (default=true, thus preserving\ncurrent behavior). Setting to false means your url will remain\nuntouched. Add drillbit unit tests. \nhttps://github.com/appcelerator/titanium_mobile/commit/bcdf46569b53...
Currently the change (.autoEncodeUrl property,which can be set\nto false to avoid auto-encoding) is only on master branch. If QA\nsets to resolve and Ralf agrees, we can cherry-pick to 1_5_X.
For Ryan, an example of using it:
\n\nvar xhr = Titanium.Network.createHTTPClient;\nxhr.autoEncodeUrl = false; // do this before calling .open()\nxhr.open('GET', 'http://myhost.com/someurl.action;jsessionid=123456');\nxhr.send();\nAwesome, thank you so much!! I'm eager for the next release.
(from [fbc043377a7e44753497c3ec0c9979c0cb53b359])\n[#2589 state:fixed-in-qa][#1491] Add\nautoEncodeUrl property to HTTPClient (default=true, thus preserving\ncurrent behavior). Setting to false means your url will remain\nuntouched. Add drillbit unit tests. \nhttps://github.com/appcelerator/titanium_mobile/commit/fbc043377a7e...
This is now in the 1_5_X branch, ready for interim release.
Bill, using your code snippet I get the fail condition on a g1\n(1.6) and using the sim (2.2)
\n[INFO] Titanium SDK version: 1.5.1 (12/15/10\n08:16 1a59cc3)
user error on my part?
1a59cc3 is before my commit. I'm the commit after that.
damnit. sorry Bill, checked in G1 (1.6) and sim (2.2) looks\ngood. [INFO] Titanium SDK version: 1.5.1 (12/15/10\n16:41 fbc0433)