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

Add USE_X_FORWARDED_HOST to configuration #11428

New Issue
Closed
opened 2025-12-29 21:45:08 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:45:08 +01:00
Owner
Copy Link

Originally created by @llamafilm on GitHub (Jul 30, 2025).

NetBox version

v4.3.2

Feature type

Change to existing functionality

Proposed functionality

I would like to be able to set USE_X_FORWARDED_HOST in configuration.py. Currently the default value is set to True in settings.py and it cannot be overridden by configuration.py.

Use case

My reverse proxy sets this header to the FQDN with no port number, and it puts the correct FQDN + port in the Host header. So when I make API calls with a custom port number, the API response includes incorrect URLs. If I set USE_X_FORWARDED_HOST=False in settings.py then everything works. But I would prefer not to modify that file.

Database changes

No response

External dependencies

No response

Originally created by @llamafilm on GitHub (Jul 30, 2025). ### NetBox version v4.3.2 ### Feature type Change to existing functionality ### Proposed functionality I would like to be able to set USE_X_FORWARDED_HOST in configuration.py. Currently the default value is set to True in settings.py and it cannot be overridden by configuration.py. ### Use case My reverse proxy sets this header to the FQDN with no port number, and it puts the correct FQDN + port in the Host header. So when I make API calls with a custom port number, the API response includes incorrect URLs. If I set `USE_X_FORWARDED_HOST=False` in settings.py then everything works. But I would prefer not to modify that file. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: under review labels 2025-12-29 21:45:08 +01:00
adam closed this issue 2025-12-29 21:45:08 +01:00
adam commented 2025-12-29 21:45:09 +01:00
Author
Owner
Copy Link

@llamafilm commented on GitHub (Jul 30, 2025):

I would be happy to make a PR for this.

@llamafilm commented on GitHub (Jul 30, 2025): I would be happy to make a PR for this.
adam commented 2025-12-29 21:45:09 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Jul 31, 2025):

You can either change this at your proxy or you can change it in local_settings if needed. We've opted not to expose this as a configuration item.

@arthanson commented on GitHub (Jul 31, 2025): You can either change this at your proxy or you can change it in local_settings if needed. We've opted not to expose this as a configuration item.
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: under review type: feature
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#11428
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?