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

Attachment viewing only works once #10759

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

Originally created by @binaryoverload on GitHub (Feb 11, 2025).

Deployment Type

Self-hosted - Deployed using Helm Chart

NetBox Version

v4.2.3-Docker-3.2.0

Python Version

3.12

Steps to Reproduce

  1. Upload an attachment to an object (i.e. an image to a site)
  2. Click on the attachment - observe successful first request
  3. Refresh the page
  4. Receive 404 with reference to ServerError.aspx

Expected Behavior

Attachment should be accessible when refreshing the attachment page, not just on first load

Observed Behavior

Image loads first time, but one refresh goes to 404 pointing at ServerError.aspx which doesn't exist

Debug view:

Image

Originally created by @binaryoverload on GitHub (Feb 11, 2025). ### Deployment Type Self-hosted - Deployed using Helm Chart ### NetBox Version v4.2.3-Docker-3.2.0 ### Python Version 3.12 ### Steps to Reproduce 1. Upload an attachment to an object (i.e. an image to a site) 2. Click on the attachment - observe successful first request 3. Refresh the page 4. Receive 404 with reference to ServerError.aspx ### Expected Behavior Attachment should be accessible when refreshing the attachment page, not just on first load ### Observed Behavior Image loads first time, but one refresh goes to 404 pointing at ServerError.aspx which doesn't exist Debug view: ![Image](https://github.com/user-attachments/assets/4f6e0465-af83-4fba-a510-d597a6d29061)
adam closed this issue 2025-12-29 21:35:39 +01:00
adam commented 2025-12-29 21:35:39 +01:00
Author
Owner
Copy Link

@binaryoverload commented on GitHub (Feb 11, 2025):

This turned out to be an issue with a Cloudflare Worker acting on Netbox - since adding the exclusion this has been fixed

@binaryoverload commented on GitHub (Feb 11, 2025): This turned out to be an issue with a Cloudflare Worker acting on Netbox - since adding the exclusion this has been fixed
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
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#10759
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?