404 errors whenever there are ? parameters on the URL

[HawthornThistleberry]

Starting within the last few days, a page that I have been using by Bitbucket Cloud for years and years has stopped working. The repository can be seen here: 

https://bitbucket.org/HawthornThistleberry/hawthornthistleberry.bitbucket.io/

Up until a few days ago I could browse to https://hawthornthistleberry.bitbucket.io/index.html?code=123456&key=ABCDEFGH (obviously not my real code and key) and the page would correctly load, whereupon the Javascript would pull those parameters and do the right thing. I actually had quite a few more parameters I used. This approach lets this page work on even small devices using no local storage and no configuration beyond the URL.

Something changed in publishing by Bitbucket Cloud (https://support.atlassian.com/bitbucket-cloud/docs/publishing-a-website-on-bitbucket-cloud/) in the last few days so now this throws a 404. If I take all the parameters off, though, and browse just to https://hawthornthistleberry.bitbucket.io/ or https://hawthornthistleberry.bitbucket.io/index.html the page clearly loads, and provides an error message (that I coded) telling me I didn't supply a code and key. So the hosting is all still working, but whatever's interpreting the URL is now incorrectly handling the ?something=something format in the URL and giving a 404 instead.

Seems to be impossible to file an actual bug report, so this is the best I can do.

[Theodora Boudale]

Hi @HawthornThistleberry and welcome to the community.

I do not see a 404 error when accessing https://hawthornthistleberry.bitbucket.io/index.html?code=123456&key=ABCDEFGH. Does this occur only when you use your own correct parameters?

Does the 404 error show that the repo is not found or something similar? Could you post a screenshot of what you see? Or are you making an API call with these codes that returns a 404 error?

I can reach out to the development team and ask them to look into this, but I would need that info first to better explain the issue.

Kind regards,
Theodora

[HawthornThistleberry]

The problem cleared up a few hours after I posted this -- I thought maybe my posting this had led to that, but probably it's just coincidence.

[Theodora Boudale]

Thank you for the update.

I assume that a deployment might have broken this, and it was later rollbacked or the issue was fixed with a subsequent deployment.

Please feel free to reach out if you ever experience any issues again.

Kind regards,
Theodora