View source not working

Mihai Voicescu

I am having a problem with my Bitbucket installation. Viewing of the source or diffs do not work anymore, after a restart.

It seems it is serializing twice on some endpoints, outputting "{\"foo\":\"bar\"}" instead of {"foo":"bar"}. For example on /rest/shortcuts/latest/shortcuts/6433dff/bundled causing the following error:

 

keycommands.js?_statichash=37818e7b0dcec195edbcd6beeb7c7a7f-CDN%2F-150220931%2F6433dff%2F1%2F3bc2d48f91521e1c446cc5b6c0571ff0&locale=en-US:formatted:1 Uncaught Error: Server returned no shortcuts.
at Object.success (keycommands.js?_statichash=37818e7b0dcec195edbcd6beeb7c7a7f-CDN%2F-150220931%2F6433dff%2F1%2F3bc2d48f91521e1c446cc5b6c0571ff0&locale=en-US:formatted:1)
at i (keycommands.js?_statichash=37818e7b0dcec195edbcd6beeb7c7a7f-CDN%2F-150220931%2F6433dff%2F1%2F3bc2d48f91521e1c446cc5b6c0571ff0&locale=en-US:formatted:1)
at Object.fireWith [as resolveWith] (keycommands.js?_statichash=37818e7b0dcec195edbcd6beeb7c7a7f-CDN%2F-150220931%2F6433dff%2F1%2F3bc2d48f91521e1c446cc5b6c0571ff0&locale=en-US:formatted:1)
at u (keycommands.js?_statichash=37818e7b0dcec195edbcd6beeb7c7a7f-CDN%2F-150220931%2F6433dff%2F1%2F3bc2d48f91521e1c446cc5b6c0571ff0&locale=en-US:formatted:1)
at XMLHttpRequest.<anonymous> (keycommands.js?_statichash=37818e7b0dcec195edbcd6beeb7c7a7f-CDN%2F-150220931%2F6433dff%2F1%2F3bc2d48f91521e1c446cc5b6c0571ff0&locale=en-US:formatted:1)

 

I think one of the plugins has registered a faulty serialiser. I entered safe mode (which should disable all user plugins) but the same problem seems to occur.

Is there any way to print all registered serializers or to see them using the JVM debug? Or does anyone have a better idea?

Evan Slaughter

Hey @Mihai Voicescu,

The best thing to do is probably to enable debug and profiler logging and then check the application/profiler logs after you reproduce the issue for any kind of strange classes or plugin output that could be modifying the output from the server for these shortcut calls.

Outside of the above, if your team is using a reverse proxy alongside Bitbucket, I'd recommend making a direct call to Bitbucket by bypassing the proxy - as this will help confirm that there's no kind of content manipulation or other changes being made at the proxy level that could be breaking anything.

If you're still are running into issues after performing these steps, I'd recommend shooting us a full support zip over at https://support.atlassian.com/contact - as it's likely we'd need to do a more in-depth investigation into your team's configuration that wouldn't be appropriate for a public forum. 

Thanks,

Evan