500 error when oauth_timestamp is in scientific notation (BB-12111)

Issue #10972 closed
Michael Edgar
created an issue

In developing a new OAuth integration, I had a bug where my Authorization header included "oauth_timestamp=1.42333209929e+12" rather than "oauth_timestamp=1423332099290".

Unlike most mistakes in formatting the Authorization header, this produced a 500 HTTP error, not a 401 or 403 HTTP error. I suspect I hit an edge case in Bitbucket's OAuth header parser.

Comments (4)

  1. Log in to comment