Details
-
Bug
-
Resolution: Invalid
-
Medium
Description
Within the past few days something has changed in the implementation of the event URI which causes the HTTP 'Content-Type' header to alternate from 'application/json' to 'text/html'. I believe it has something to do with a caching mechanism since it seems to report the correct Content-Type in a first request and subsequent requests return the 'text/html' Content-Type:
My first request to: https://api.bitbucket.org/1.0/users/thedillonb/events/\\
Returns: Content-Type →application/json; charset=utf-8
My second request to: https://api.bitbucket.org/1.0/users/thedillonb/events/\\
Returns: Content-Type →text/html; charset=utf-8
And will continue to return 'text/html' for a while.
The body is still JSON in both cases but the 'Content-Type' is incorrect in some cases.