Custom link HREF empty #17949
-
Deployment TypeSelf-hosted Triage priorityN/A NetBox Versionv4.1.6 Python Version3.12.3 Steps to Reproduce
Expected BehaviorWhen clicking the button it should open the webpage. Observed BehaviorThe href seems to be empty:
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 3 replies
-
This works as expected. Check your |
Beta Was this translation helpful? Give feedback.
-
Hi @jeremystretch and thanks. However: It was previously set to *. Now I have Allowed URL schemes ('http','https','telnet','ssh','vnc') but still no luck. Still empty refs. This netbox is running behind a HA-proxy. All sorts forwarded-headers are provided, esp. http-request set-header X-Forwarded-Proto https What else could I be looking for? |
Beta Was this translation helpful? Give feedback.
-
Thanks setting it back shows the default is file, ftp, ftps, http, https, irc, mailto, sftp, ssh, tel, telnet, tftp, vnc, xmpp so without ('') around it (which I found in the documents but maybe they just very successfully confused me. I was aware of what the parameter was supposed to do. Just that this discussion suggested that it will only work with correct X-Forwarded- headers (which does not make a lot of sense to be but hey....): #6862 It is working now! Thanks! |
Beta Was this translation helpful? Give feedback.
-
The link URL must be just a URL. No "anything. else. " in front of it. |
Beta Was this translation helpful? Give feedback.
ALLOWED_URL_SCHEMES
is used solely for the sanitization of user-submitted hyperlinks; it has nothing to do with how NetBox itself is running. Try removing the config parameter (restoring the default) and restarting NetBox.