{ "id": "62044", "key": "TIMOB-1412", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [ { "id": "11225", "name": "Release 1.5.0", "archived": true, "released": true, "releaseDate": "2010-12-14" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2011-04-17T01:56:06.000+0000", "created": "2011-04-15T02:51:39.000+0000", "priority": { "name": "Low", "id": "4" }, "labels": [ "https", "ios", "iphone" ], "versions": [], "issuelinks": [], "assignee": { "name": "stephentramer", "key": "stephentramer", "displayName": "Stephen Tramer", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2011-04-17T01:56:06.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "10206", "name": "iOS", "description": "iOS Platform" } ], "description": "{html}

From blog post...

\n

There is a thread on the QA on HTTPS being broken. This broke in\na fairly recent build as we were using the nightly from a week or\ntwo ago with no issue. URL formats like this: https://username:password@api.lafitness.com\nwill fail 100% of the
\ntime. Take out https and just go with http and it works fine. Our\ncert is not self signed.

\n

I think this might be related to the UTF-8 URI change (although,\nthat should effect both http right?).

{html}", "attachment": [ { "id": "17985", "filename": "resources.zip", "author": { "name": "zeroendless", "key": "zeroendless", "displayName": "zeroendless", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2011-04-15T02:51:39.000+0000", "size": 146064, "mimeType": "application/zip" } ], "flagged": false, "summary": "iPhone: username/pass on URL (https only?) will break", "creator": { "name": "jhaynie", "key": "jhaynie", "displayName": "Jeff Haynie", "active": false, "timeZone": "America/Los_Angeles" }, "subtasks": [], "reporter": { "name": "jhaynie", "key": "jhaynie", "displayName": "Jeff Haynie", "active": false, "timeZone": "America/Los_Angeles" }, "environment": null, "comment": { "comments": [ { "id": "125596", "author": { "name": "zeroendless", "key": "zeroendless", "displayName": "zeroendless", "active": true, "timeZone": "America/Los_Angeles" }, "body": "{html}

I have twitter Xauth with similar posting issues. it've been\nworking great on 1.3.2 and early 1.3.3 built version with iOS 4/iOS\n4.01, but refused to work on 1.4. I can reserve it back to early\nversion and it would work again.

\n

I attached files for testing if that helps speed up the\nprogress. With 1.4, i always get authentication error \"Error\nDomain=ASIHTTPRequestErrorDomain Code=3 \"Authentication needed\"\nUserInfo=0x7a1cbd0 {NSLocalizedDescription=Authentication needed\"\ndespite all parameters checked and submit as requested, including a\nvalid pair of twitter username and password. It seems like there's\nproblem with parameters encoding issue on 1.4 too?

\n

Thanks

{html}", "updateAuthor": { "name": "zeroendless", "key": "zeroendless", "displayName": "zeroendless", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2011-04-15T02:51:39.000+0000", "updated": "2011-04-15T02:51:39.000+0000" }, { "id": "125597", "author": { "name": "jhaynie", "key": "jhaynie", "displayName": "Jeff Haynie", "active": false, "timeZone": "America/Los_Angeles" }, "body": "{html}

(from [60364b73b1c5d17d7e8f42ecaf80b58efb5e5d4f])\n[#1412 state:resolved] CFURLCreateStringBy...\nautomatically doesn't substitute escapes for valid URL characters.\n\nhttp://github.com/appcelerator/titanium_mobile/commit/60364b73b1c5d...

{html}", "updateAuthor": { "name": "jhaynie", "key": "jhaynie", "displayName": "Jeff Haynie", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2011-04-15T02:51:40.000+0000", "updated": "2011-04-15T02:51:40.000+0000" }, { "id": "125598", "author": { "name": "zeroendless", "key": "zeroendless", "displayName": "zeroendless", "active": true, "timeZone": "America/Los_Angeles" }, "body": "{html}

Hi Jeff,
\nThanks for the quick attention.

\n

I tried the patch, copy the util file to 1.4 but still having\nthe same issue on Twitter Xauth posting.

\n

Thanks

{html}", "updateAuthor": { "name": "zeroendless", "key": "zeroendless", "displayName": "zeroendless", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2011-04-15T02:51:40.000+0000", "updated": "2011-04-15T02:51:40.000+0000" }, { "id": "125599", "author": { "name": "stephentramer", "key": "stephentramer", "displayName": "Stephen Tramer", "active": true, "timeZone": "America/Los_Angeles" }, "body": "{html}

The problem appears to be this:

\n
\n

['oauth_signature_method', 'HMAC-SHA1'],

\n
\n

I took a look at the generated URL, and this is the only portion\nof it which was escaped:

\n
\n

oauth_signature=imhFTmernI9uy7a2keXj%2FEWoC%2BE%3D

\n
\n

HMAC-SHA1 may be placing unicode characters which would normally\nneed to be escaped into your authorization string. I would\nrecommend using a different signature method, since there is no\nworkaround for this on our end.

{html}", "updateAuthor": { "name": "stephentramer", "key": "stephentramer", "displayName": "Stephen Tramer", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2011-04-15T02:51:41.000+0000", "updated": "2011-04-15T02:51:41.000+0000" }, { "id": "125600", "author": { "name": "jhaynie", "key": "jhaynie", "displayName": "Jeff Haynie", "active": false, "timeZone": "America/Los_Angeles" }, "body": "{html}

i think the problem is that we're escaping twice. the path\nshould be escaped on our end but not the entire query string. this\nis a platform problem i believe since this worked before this\nchange.

{html}", "updateAuthor": { "name": "jhaynie", "key": "jhaynie", "displayName": "Jeff Haynie", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2011-04-15T02:51:41.000+0000", "updated": "2011-04-15T02:51:41.000+0000" }, { "id": "125601", "author": { "name": "jhaynie", "key": "jhaynie", "displayName": "Jeff Haynie", "active": false, "timeZone": "America/Los_Angeles" }, "body": "{html}

(from [3bca7969873c164f4596a1249a2f1f5e0143e172])\n[#1412 state:resolved] Original list of\ncharacters to not escape was right... just not the right argument.\n\nhttp://github.com/appcelerator/titanium_mobile/commit/3bca7969873c1...

{html}", "updateAuthor": { "name": "jhaynie", "key": "jhaynie", "displayName": "Jeff Haynie", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2011-04-15T02:51:41.000+0000", "updated": "2011-04-15T02:51:41.000+0000" }, { "id": "125602", "author": { "name": "lukemelia", "key": "lukemelia", "displayName": "Luke Melia", "active": true, "timeZone": "America/Los_Angeles" }, "body": "{html}

I had this problem and can confirm that\n3bca7969873c164f4596a1249a2f1f5e0143e172 fixed it for me.\nThanks.

{html}", "updateAuthor": { "name": "lukemelia", "key": "lukemelia", "displayName": "Luke Melia", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2011-04-15T02:51:41.000+0000", "updated": "2011-04-15T02:51:41.000+0000" }, { "id": "125603", "author": { "name": "zeroendless", "key": "zeroendless", "displayName": "zeroendless", "active": true, "timeZone": "America/Los_Angeles" }, "body": "{html}

Brilliant, Thanks.

{html}", "updateAuthor": { "name": "zeroendless", "key": "zeroendless", "displayName": "zeroendless", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2011-04-15T02:51:41.000+0000", "updated": "2011-04-15T02:51:41.000+0000" } ], "maxResults": 8, "total": 8, "startAt": 0 } } }