{
	"id": "168480",
	"key": "AC-5037",
	"fields": {
		"issuetype": {
			"id": "1",
			"description": "A problem which impairs or prevents the functions of the product.",
			"name": "Bug",
			"subtask": false
		},
		"project": {
			"id": "12217",
			"key": "AC",
			"name": "Appcelerator - INBOX",
			"projectCategory": {
				"id": "10000",
				"description": "",
				"name": "Customer Service"
			}
		},
		"resolution": {
			"id": "6",
			"description": "",
			"name": "Hold"
		},
		"resolutiondate": "2017-06-23T18:29:02.000+0000",
		"created": "2017-06-19T05:01:37.000+0000",
		"labels": [
			"android"
		],
		"versions": [],
		"issuelinks": [],
		"assignee": {
			"name": "shossain",
			"key": "shossain",
			"displayName": "Shak Hossain",
			"active": false,
			"timeZone": "America/Los_Angeles"
		},
		"updated": "2017-06-23T18:29:02.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": "14548",
				"name": "Titanium SDK & CLI",
				"description": "Please enter tickets related to the MobileSDK here."
			}
		],
		"description": "I wish to force my existing clients from http:// > https:// to do this I have automatic https rewrites turned on on my domain.\r\n\r\nThis works fine on iOS, the 301 redirect is followed and the HTTPClient follows the redirect. On Android this is not the case. I am using the latest SDK 6.1.0GA (all SDK versions have this bug as far as I can see).\r\n\r\nFor example if you go to: http://uk.markive.co.uk you will see in Chrome the 301 redirect to https://. In iOS this a httpclient connection to this URL will redirect on Android it will throw and error.\r\n\r\nThis is not consistent..\r\n\r\n",
		"attachment": [],
		"flagged": false,
		"summary": "http 301 redirect (http > https) does not work (still) in Android",
		"creator": {
			"name": "mark.henderson@snagr.co.uk",
			"key": "mark.henderson@snagr.co.uk",
			"displayName": "Mark Henderson",
			"active": true,
			"timeZone": "Europe/London"
		},
		"subtasks": [],
		"reporter": {
			"name": "mark.henderson@snagr.co.uk",
			"key": "mark.henderson@snagr.co.uk",
			"displayName": "Mark Henderson",
			"active": true,
			"timeZone": "Europe/London"
		},
		"environment": "Latest SDK",
		"comment": {
			"comments": [
				{
					"id": "422217",
					"author": {
						"name": "ybanev",
						"key": "ybanev",
						"displayName": "Yordan Banev",
						"active": true,
						"timeZone": "Europe/Athens"
					},
					"body": "Hello! Would you be able to provide a code snippet that reproduces the issue?",
					"updateAuthor": {
						"name": "ybanev",
						"key": "ybanev",
						"displayName": "Yordan Banev",
						"active": true,
						"timeZone": "Europe/Athens"
					},
					"created": "2017-06-19T09:05:42.000+0000",
					"updated": "2017-06-19T09:05:42.000+0000"
				},
				{
					"id": "422341",
					"author": {
						"name": "mark.henderson@snagr.co.uk",
						"key": "mark.henderson@snagr.co.uk",
						"displayName": "Mark Henderson",
						"active": true,
						"timeZone": "Europe/London"
					},
					"body": "I can see that if I make a 'GET' then autoredirect does work in Android as it does in iOS. If I make a 'POST' then it doesn't redirect. \r\n\r\nApparently this can be dangerous if you auto-direct based on a POST, so I am ok to close.",
					"updateAuthor": {
						"name": "mark.henderson@snagr.co.uk",
						"key": "mark.henderson@snagr.co.uk",
						"displayName": "Mark Henderson",
						"active": true,
						"timeZone": "Europe/London"
					},
					"created": "2017-06-20T02:41:22.000+0000",
					"updated": "2017-06-20T02:41:22.000+0000"
				}
			],
			"maxResults": 2,
			"total": 2,
			"startAt": 0
		}
	}
}