Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error 404 when the path in the base URL is not empty #122

Closed
m4r1vs opened this issue Nov 8, 2024 · 3 comments
Closed

Error 404 when the path in the base URL is not empty #122

m4r1vs opened this issue Nov 8, 2024 · 3 comments

Comments

@m4r1vs
Copy link
Contributor

m4r1vs commented Nov 8, 2024

Desktop (please complete the following information):

  • OS: Linux 6.11.6-arch1-1
  • Terminal Alacritty
  • Architecture: x86
  • Fjira version: From source (commit db02e39)

Describe the bug
When the API URL includes a path, after initializing fjira, I do not get a
list of projects but a 404 instead.

To Reproduce
Steps to reproduce the behavior:

Set config like this

current: default
workspaces:
    default:
        jiraRestUrl: https://tgipm.informatik.uni-hamburg.de/jira/
        jiraToken: TOKEN
        iraUsername: USERNAME
        jiraTokenType: personal token

Run fjira. Notice the /jira in the path of jiraRestUrl. The error is caused by https://tgipm.informatik.uni-hamburg.de/restApi being called instead of https://tgipm.informatik.uni-hamburg.de/jira/restApi.

Expected behavior
See project list.

Actual Behavior
Get Error 404

Additional notes

@mk-5
Copy link
Owner

mk-5 commented Nov 12, 2024

@m4r1vs thanks for a report! I will check PR right away

@mk-5
Copy link
Owner

mk-5 commented Nov 12, 2024

@m4r1vs I've merged it - but I think it would be nice to add some unit test for that paths combine logic. I will add it

@mk-5
Copy link
Owner

mk-5 commented Nov 13, 2024

fixed in 1.4.4

@mk-5 mk-5 closed this as completed Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants