{
	"id": "62781",
	"key": "TIMOB-2149",
	"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": [],
		"resolution": {
			"id": "7",
			"description": "",
			"name": "Invalid"
		},
		"resolutiondate": "2011-04-15T03:11:58.000+0000",
		"created": "2011-04-15T03:11:56.000+0000",
		"priority": {
			"name": "Medium",
			"id": "3"
		},
		"labels": [
			"defect",
			"ios",
			"iphone",
			"xhr"
		],
		"versions": [],
		"issuelinks": [],
		"assignee": {
			"name": "rpfeiffer",
			"key": "rpfeiffer",
			"displayName": "Ralf Pfeiffer",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"updated": "2017-03-09T23:04:10.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}<div><p>When sending a request to XHR to the following URL:</p>\n<p><a href=\n\"http://mike@demandocat.com:testing@api.lafitness.com/Services/Private.svc/GetCustomer\">\nhttp://mike@demandocat.com:testing@api.lafitness.com/Services/Priva...</a></p>\n<p>The request is directed to demandocat.com instead of\napi.lafitness.com.</p>\n<p>Some sort of issue exists parsing URLs that contain\nusername/passwords when they contain the @ char.</p></div>{html}",
		"attachment": [],
		"flagged": false,
		"summary": "Android, parse problem with URLs that contain @ in username ",
		"creator": {
			"name": "bryanjackson",
			"key": "bryanjackson",
			"displayName": "Bryan Jackson",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"subtasks": [],
		"reporter": {
			"name": "bryanjackson",
			"key": "bryanjackson",
			"displayName": "Bryan Jackson",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"environment": null,
		"comment": {
			"comments": [
				{
					"id": "127636",
					"author": {
						"name": "bryanjackson",
						"key": "bryanjackson",
						"displayName": "Bryan Jackson",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "{html}<div><p>Note the title should say iPhone not Android</p></div>{html}",
					"updateAuthor": {
						"name": "bryanjackson",
						"key": "bryanjackson",
						"displayName": "Bryan Jackson",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2011-04-15T03:11:57.000+0000",
					"updated": "2011-04-15T03:11:57.000+0000"
				},
				{
					"id": "127637",
					"author": {
						"name": "dthorp",
						"key": "dthorp",
						"displayName": "Don Thorp",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "{html}<div><p>Fixed title to reflect iPhone, not Android.</p></div>{html}",
					"updateAuthor": {
						"name": "dthorp",
						"key": "dthorp",
						"displayName": "Don Thorp",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2011-04-15T03:11:57.000+0000",
					"updated": "2011-04-15T03:11:57.000+0000"
				},
				{
					"id": "127638",
					"author": {
						"name": "rpfeiffer",
						"key": "rpfeiffer",
						"displayName": "Ralf Pfeiffer",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "{html}<div><p>to scrub</p></div>{html}",
					"updateAuthor": {
						"name": "rpfeiffer",
						"key": "rpfeiffer",
						"displayName": "Ralf Pfeiffer",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2011-04-15T03:11:58.000+0000",
					"updated": "2011-04-15T03:11:58.000+0000"
				},
				{
					"id": "127639",
					"author": {
						"name": "blainhamon",
						"key": "blainhamon",
						"displayName": "Blain Hamon",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "{html}<div><p><a href=\n\"http://www.ietf.org/rfc/rfc3986.txt\">http://www.ietf.org/rfc/rfc3986.txt</a></p>\n<p>The authority (Username and host info) is defined as [ userinfo\n\"@\" ] host [ \":\" port ]</p>\n<p>userinfo is defined as *( unreserved / pct-encoded / sub-delims\n/ \":\" )</p>\n<p>unreserved is defined as ALPHA / DIGIT / \"-\" / \".\" / \"_\" /\n\"~\"</p>\n<p>pct-encoded is defined as \"%\" HEXDIG HEXDIG</p>\n<p>sub-delims is defined as \"!\" / \"$\" / \"&amp;\" / \"'\" / \"(\" / \")\" /\n\"*\" / \"+\" / \",\" / \";\" / \"=\"</p>\n<p>In none of userinfo is \"@\" allowed as a valid character.</p>\n<p>Per rfc 3986, the URI is requesting host of demandocat.com, port\n'testing', which is an invalid number. Thus, this URI is\ninvalid.</p>\n<p>To specify a userinfo that would contain the \"@\" character, it\nMUST be pct-encoded as \"%40\"</p></div>{html}",
					"updateAuthor": {
						"name": "blainhamon",
						"key": "blainhamon",
						"displayName": "Blain Hamon",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2011-04-15T03:11:58.000+0000",
					"updated": "2011-04-15T03:11:58.000+0000"
				},
				{
					"id": "127640",
					"author": {
						"name": "fairwinds",
						"key": "fairwinds",
						"displayName": "David Pratt",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "{html}<div><p>Invalidated without any evaluation to ensure authentication is\npossible using this means or test case for basic auth? The ability\nfor a client to pass credentials by this means is very basic\nfunctionality. It does not work with this client with iOS.</p>\n<p>Before closing or invalidating the ticket, it would be\npreferable to demonstrate that the functionality performs as\nexpected or repair/assign if it does not. This issue has been\nsatisfactorily repaired for Android with a test confirmation one\ncan now properly authenticate. I feel this has been evaded. This is\nnecessary functionality for web services work and we have a\ncrippled client if it cannot perform basic authentication using\nthis method.</p></div>{html}",
					"updateAuthor": {
						"name": "fairwinds",
						"key": "fairwinds",
						"displayName": "David Pratt",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2011-04-15T03:11:58.000+0000",
					"updated": "2011-04-15T03:11:58.000+0000"
				},
				{
					"id": "127641",
					"author": {
						"name": "fairwinds",
						"key": "fairwinds",
						"displayName": "David Pratt",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "{html}<div><p>Blain. I can put together something that demonstrates the\ninability to authenticate by passing credentials in url where doing\nsame in curl succeeds. Passing credentials in this way is a common\nthing to want to do and this requires a fix.</p></div>{html}",
					"updateAuthor": {
						"name": "fairwinds",
						"key": "fairwinds",
						"displayName": "David Pratt",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2011-04-15T03:11:58.000+0000",
					"updated": "2011-04-15T03:11:58.000+0000"
				},
				{
					"id": "127642",
					"author": {
						"name": "rpfeiffer",
						"key": "rpfeiffer",
						"displayName": "Ralf Pfeiffer",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "{html}<div><p>Hello fairwinds,</p>\n<p>Our current situation:</p>\n<p>With URLs, we have already gone down the slippery slope in\nTitanium. I would have preferred that we were strict in the main\nAPI, and yet also provide helper functions to encode/decode,\nescape, where the algorithms are well-documented and\nunderstood.</p>\n<p>In the coming months we will systematically scrub our API and\nseek to achieve a good balance between achieving better standards\ncompliance as well providing functionality for ease of use by the\nend developer.</p>\n<p>On this specific issue:</p>\n<p>Blain's comment is accurate, that \"@\" is not allowed in the\nuserinfo, and that if non-allowed characters exist, they should be\nescaped. In this case if \"@\" is the userinfo should be \"%40\".</p>\n<p>What we will do:</p>\n<p>We'll take the action to discuss this issue internally, as\nAndroid and iOS differ in their approach right now.</p>\n<p>Thanks for your input, and expect an update on this within a\nweek.</p>\n<p>Sincerely,<br>\n~Ralf Dir of Platform Engineering</p></div>{html}",
					"updateAuthor": {
						"name": "rpfeiffer",
						"key": "rpfeiffer",
						"displayName": "Ralf Pfeiffer",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2011-04-15T03:11:58.000+0000",
					"updated": "2011-04-15T03:11:58.000+0000"
				},
				{
					"id": "127643",
					"author": {
						"name": "fairwinds",
						"key": "fairwinds",
						"displayName": "David Pratt",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "{html}<div><p>Hi Ralph. Not sure the issue for me was properly characterized\nby the ticket. The core issue for me is not simply the @ in the\nname but authenticating via:</p>\n<p><a href=\n\"http://user:pw@example.com\">http://user:pw@example.com</a> or<br>\n<a href=\n\"http://user:pw@example.com\">http://user:pw@example.com</a></p>\n<p>neither of which will authenticate using the client. Am quite\nhappy to encode the user:pw string including any @ character that\nmight exist there.</p></div>{html}",
					"updateAuthor": {
						"name": "fairwinds",
						"key": "fairwinds",
						"displayName": "David Pratt",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2011-04-15T03:11:59.000+0000",
					"updated": "2011-04-15T03:11:59.000+0000"
				},
				{
					"id": "127644",
					"author": {
						"name": "fairwinds",
						"key": "fairwinds",
						"displayName": "David Pratt",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "{html}<div><p>Ralph. One of those examples should be https above, sorry for\ntypo.</p></div>{html}",
					"updateAuthor": {
						"name": "fairwinds",
						"key": "fairwinds",
						"displayName": "David Pratt",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2011-04-15T03:11:59.000+0000",
					"updated": "2011-04-15T03:11:59.000+0000"
				},
				{
					"id": "410906",
					"author": {
						"name": "lmorris",
						"key": "lmorris",
						"displayName": "Lee Morris",
						"active": false,
						"timeZone": "America/Los_Angeles"
					},
					"body": "Closing ticket as invalid.",
					"updateAuthor": {
						"name": "lmorris",
						"key": "lmorris",
						"displayName": "Lee Morris",
						"active": false,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2017-03-09T23:04:10.000+0000",
					"updated": "2017-03-09T23:04:10.000+0000"
				}
			],
			"maxResults": 10,
			"total": 10,
			"startAt": 0
		}
	}
}