Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] 404 Error page responds with 200 HTTP code #1136

Closed
5 tasks done
sambartik opened this issue Mar 8, 2023 · 6 comments
Closed
5 tasks done

[BUG] 404 Error page responds with 200 HTTP code #1136

sambartik opened this issue Mar 8, 2023 · 6 comments
Assignees
Labels
🐛 Bug [ISSUE] Ticket describing something that isn't working

Comments

@sambartik
Copy link

Environment

Self-Hosted (Docker)

System

No response

Version

2.1.1

Describe the problem

Hello, I have been using dashy for a while now. I have configured my own logic for 404 error pages via nginx. Today I have noticed that instead of my own logic I got shown the new native Dashy's 404 error page.

In my configuration, the Dashy is behind a reverse proxy that handles the traffic. I have my own way of handling when Dashy would return a 404 error. However, now it fails, because Dashy returns /404 page with an HTTP 200 OK status.

Reverting back to version 2.1.0 fixed the issue.

Additional info

No response

Please tick the boxes

@sambartik sambartik added the 🐛 Bug [ISSUE] Ticket describing something that isn't working label Mar 8, 2023
@liss-bot
Copy link
Collaborator

liss-bot commented Mar 8, 2023

If you're enjoying Dashy, consider dropping us a ⭐
🤖 I'm a bot, and this message was automated

@liss-bot
Copy link
Collaborator

liss-bot commented Apr 8, 2023

This issue has gone 6 weeks without an update. To keep the ticket open, please indicate that it is still relevant in a comment below. Otherwise it will be closed in 5 working days.

@liss-bot liss-bot added the ⚰️ Stale [ISSUE] [PR] No activity for over 1 month label Apr 8, 2023
@liss-bot
Copy link
Collaborator

This issue was automatically closed because it has been stalled for over 6 weeks with no activity.

@liss-bot liss-bot removed the ⚰️ Stale [ISSUE] [PR] No activity for over 1 month label Apr 13, 2023
@shellshock1953
Copy link

shellshock1953 commented Jan 24, 2024

Same here - can we reopen this one?

@Lissy93
Copy link
Owner

Lissy93 commented Feb 28, 2024

I'm actually not sure that this ever worked.

Reason being, in Vue all the routing is handled on the client side, so the server serves up the same file whatever route you visit (it's always index.html), which then renders whatever it needs (or a "not found" message if nothing matches).

That said, I can implement logic in the Node server to respond with a 404 status when the index.html itself is not found.

If this used to work for you, could it have been a change that you made in your reverse proxy config?

@Lissy93 Lissy93 closed this as completed in 27995f8 Mar 3, 2024
@github-project-automation github-project-automation bot moved this from Awaiting Triage to Done in Dashy V3 Mar 3, 2024
@liss-bot
Copy link
Collaborator

liss-bot commented Mar 3, 2024

The fix for this issue has now been released in 2.1.2 ✨

If you haven't done so already, please update your instance to 2.1.2 or later. See 2.1.2 for full info.

Feel free to reach out if you need any more support. If you are enjoying Dashy, consider supporting the project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug [ISSUE] Ticket describing something that isn't working
Projects
Status: Done
Development

No branches or pull requests

4 participants