Usernames in API requests should not be Case Sensitive (BB-1879)

Brad Montgomery avatarBrad Montgomery created an issue

Similar to Issues #234, #421, requests to the API that include a username are case sensitive. It would be great if the api would return the correct info for a user regardless of the case.

Comments (6)

  1. David Chambers

    Unfortunately in its early days Bitbucket allowed usernames to differ only in case (e.g. "bob" and "Bob" could coexist as distinct users). In light of this fact would it actually be helpful for us to match in a case-insensitive fashion where possible, or would the inconsistent behaviour trip unsuspecting developers?

  2. dillonbwpo

    I absolutely agree. If you can log into the site with a case insensitive name then you should be able to make API requests with that same case insensitive name! It's confusing for services that use the API to be able to successfully authenticate but the requests to, say get your events, returns a Not Found error condition.

  3. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.