starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

URLs for devices on Front/Rear rack does not persist protocol #3765

New Issue
Closed
opened 2025-12-29 18:31:07 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:31:07 +01:00
Owner
Copy Link

Originally created by @DSpeichert on GitHub (Jun 10, 2020).

Environment

  • Python version: Python 3.7.7
  • NetBox version: 8c15eb0d4d28 (v2.8.5)

Steps to Reproduce

  1. Add any device to a rack
  2. Click on the device on the rack visualization (at the RU)
  3. You jump from a https:// to http://

Expected Behavior

Link should be relative or take protocol into account.

Observed Behavior

Netbox generates an absolute link but using http:// when the current protocol in use is https://.

I deployed using https://github.com/netbox-community/netbox-docker and run TLS using hitch proxy. I looked through configuration and there is no documented "Base URL" option that I could configure to make Netbox generate correct URLs.

I think it would be easiest to just use relative URL there as well.

Originally created by @DSpeichert on GitHub (Jun 10, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report, and that any plugins have been disabled. --> ### Environment * Python version: Python 3.7.7 * NetBox version: 8c15eb0d4d28 (v2.8.5) <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox. Begin with the creation of any necessary database objects and call out every operation being performed explicitly. If reporting a bug in the REST API, be sure to reconstruct the raw HTTP request(s) being made: Don't rely on a client library such as pynetbox. --> ### Steps to Reproduce 1. Add any device to a rack 2. Click on the device on the rack visualization (at the RU) 3. You jump from a `https://` to `http://` <!-- What did you expect to happen? --> ### Expected Behavior Link should be relative or take protocol into account. <!-- What happened instead? --> ### Observed Behavior Netbox generates an absolute link but using `http://` when the current protocol in use is `https://`. I deployed using https://github.com/netbox-community/netbox-docker and run TLS using [hitch proxy](https://github.com/netbox-community/netbox-docker/wiki/TLS). I looked through configuration and there is no documented "Base URL" option that I could configure to make Netbox generate correct URLs. I think it would be easiest to just use relative URL there as well.
adam added the status: duplicate label 2025-12-29 18:31:07 +01:00
adam closed this issue 2025-12-29 18:31:07 +01:00
adam commented 2025-12-29 18:31:07 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 10, 2020):

Another duplicate of #4526. Your HTTP frontend must be configured to forward the protocol to the WSGI worker.

@jeremystretch commented on GitHub (Jun 10, 2020): Another duplicate of #4526. Your HTTP frontend must be configured to forward the protocol to the WSGI worker.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#3765
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?