Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,364,905
Community Members
 
Community Events
168
Community Groups

Bug: wrong content-type returned by Service Desk login page

Edited

When retrieving the Service Desk login page (e.g., https://jira.softwareplant.com/servicedesk/customer/portal/1/user/login), if 'Accept' header is not specified, the response contains 'Content-Type: application/octet-stream' rather than 'text/html'.

$ curl -I -v -H 'Accept:' https://jira.softwareplant.com/servicedesk/customer/portal/1/user/login* Trying 18.184.86.245...
* Connected to jira.softwareplant.com (18.184.86.245) port 443 (#0)

[...]
> HEAD /servicedesk/customer/portal/1/user/login HTTP/1.1
> Host: jira.softwareplant.com
> User-Agent: curl/7.47.0
>
< HTTP/1.1 200
< Date: Fri, 12 Jun 2020 12:00:53 GMT
< Content-Type: application/octet-stream;charset=UTF-8

[...]

If the Accept header is specified, and is different than '*/*', the 'Content-Type' in the response is identical to the 'Accept' header:

$ curl -I -v -H 'Accept:xxx/yyy' https://jira.softwareplant.com/servicedesk/customer/portal/1/user/login

[...]

> HEAD /servicedesk/customer/portal/1/user/login HTTP/1.1
> Host: jira.softwareplant.com
> User-Agent: curl/7.47.0
> Accept:xxx/yyy
>
< HTTP/1.1 200
< Date: Fri, 12 Jun 2020 12:06:15 GMT
< Content-Type: xxx/yyy;charset=UTF-8

[...]

 

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events