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

Failed to load resource, 404 while using BASE_PATH #7162

Closed
silkofix opened this issue Sep 3, 2021 · 5 comments · Fixed by #7218
Closed

Failed to load resource, 404 while using BASE_PATH #7162

silkofix opened this issue Sep 3, 2021 · 5 comments · Fixed by #7218
Assignees
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@silkofix
Copy link

silkofix commented Sep 3, 2021

NetBox version

v3.0.1

Python version

3.9

Steps to Reproduce

  1. Go to IPAM -> VLANs
  2. Click "Add"

Expected Behavior

Get all of searching fields like: "Tags", "Role", "VLAN Group"

Observed Behavior

I used BASE_PATH = 'netbox/'
Get a red box and api error.
netbox.js:8 GET https://localhost/netbox/netbox/api/ipam/roles/?brief=true 404 (Not Found)
I think the problem is in the link being created, it is duplicated.

When i removed BASE_PATH and use netbox like https://localhost/.
Link be like: https://localhost/api/ipam/roles/?brief=true and no problems further

@silkofix silkofix added the type: bug A confirmed report of unexpected behavior in the application label Sep 3, 2021
@ziggekatten
Copy link

We use BASE_PATH and do NOT have this problem i 3.0.1.

@silkofix
Copy link
Author

silkofix commented Sep 3, 2021

We use BASE_PATH and do NOT have this problem i 3.0.1.

ye i was reading #7091 :) But... Same problem was on 3.0.0
Maybe its problem with my proxy, but i don't think so... This problem was not on v2.11.12

@DanSheps DanSheps added the status: under review Further discussion is needed to determine this issue's scope and/or implementation label Sep 3, 2021
@DanSheps
Copy link
Member

DanSheps commented Sep 3, 2021

Could anyone else confirm if this is an issue or not?

@jeremystretch
Copy link
Member

jeremystretch commented Sep 3, 2021

Yes, this is a problem on the current develop branch. It looks like the base path is being added twice.

@jeremystretch jeremystretch added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation and removed status: under review Further discussion is needed to determine this issue's scope and/or implementation labels Sep 3, 2021
@jeremystretch
Copy link
Member

Looks like this is a regression introduced under #7091. I think I have it sorted.

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Sep 3, 2021
@jeremystretch jeremystretch self-assigned this Sep 3, 2021
jeremystretch added a commit that referenced this issue Sep 8, 2021
Fixes #7162: Decouple base path rendering from API request logic
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
4 participants