You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The api-path field for Bitbucket Server isn't usually "2.0" like it's described in all application.yml resources or in the wiki documentation examples and descriptions, it (usually) has to be redefined to be empty or a single path /, so one won't receive a 404 error like this HttpClientErrorException$NotFound: 404.
Expected Behavior
Having documented in Bitbucket's Configuration section the differences when setting the api-path parameter between Bitbucket Cloud and Server, for Bitbucket Server there should be a statement on how to set the api-path, like simply using an empty parameter or having only the initial path's backslash like api-path: / or any other applicable options.
Actual Behavior
No documentation stating the differences between the API versions and paths on Bitbucket Cloud and Server. When leaving the /2.0 on the api-path for a Bitbucket Server, a 404 error will be received, but only when debugging we see the URL looks like https://<Bitbucket URL>/rest/api/1.0/2.0/ and the /2.0 shows up after the /1.0.
The text was updated successfully, but these errors were encountered:
Description
The
api-path
field for Bitbucket Server isn't usually "2.0" like it's described in all application.yml resources or in the wiki documentation examples and descriptions, it (usually) has to be redefined to be empty or a single path/
, so one won't receive a 404 error like thisHttpClientErrorException$NotFound: 404
.Expected Behavior
Having documented in Bitbucket's Configuration section the differences when setting the
api-path
parameter between Bitbucket Cloud and Server, for Bitbucket Server there should be a statement on how to set theapi-path
, like simply using an empty parameter or having only the initial path's backslash likeapi-path: /
or any other applicable options.Actual Behavior
No documentation stating the differences between the API versions and paths on Bitbucket Cloud and Server. When leaving the
/2.0
on theapi-path
for a Bitbucket Server, a 404 error will be received, but only when debugging we see the URL looks likehttps://<Bitbucket URL>/rest/api/1.0/2.0/
and the/2.0
shows up after the/1.0
.The text was updated successfully, but these errors were encountered: