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

Add note about trailing backslash in GraphQL documentation #10340

New Issue
Closed
opened 2025-12-29 21:30:15 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:30:15 +01:00
Owner
Copy Link

Originally created by @dannywade on GitHub (Oct 9, 2024).

Change Type

Addition

Area

Integrations/API

Proposed Changes

Add note or other callout in GraphQL documentation to remind users to include trailing backslash when calling on the /graphql endpoint, so GraphQL API requests should look like this: https://netbox.com/graphql/. This may have been an issue called out in the past, but I believe it should be mentioned in the documentation so that users are not constantly fighting 301 or 400 HTTP status codes due to a missing backslash.

Originally created by @dannywade on GitHub (Oct 9, 2024). ### Change Type Addition ### Area Integrations/API ### Proposed Changes Add note or other callout in GraphQL documentation to remind users to include trailing backslash when calling on the `/graphql` endpoint, so GraphQL API requests should look like this: `https://netbox.com/graphql/`. This may have been an issue called out in the past, but I believe it should be mentioned in the documentation so that users are not constantly fighting 301 or 400 HTTP status codes due to a missing backslash.
adam added the type: documentationnetbox labels 2025-12-29 21:30:15 +01:00
adam closed this issue 2025-12-29 21:30:15 +01:00
adam commented 2025-12-29 21:30:15 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 7, 2025):

This may have been an issue on previous releases, but I can confirm that NetBox v4.2.3 at least automatically redirects from /graphql to /graphql/, so I don't think any note is needed.

@jeremystretch commented on GitHub (Feb 7, 2025): This may have been an issue on previous releases, but I can confirm that NetBox v4.2.3 at least automatically redirects from `/graphql` to `/graphql/`, so I don't think any note is needed.
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 netbox type: documentation
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#10340
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?