-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Custom 500 page content-type is text/plain;charset=UTF-8 #7992
Copy link
Copy link
Closed
Labels
- P2: has workaroundAn edge case that only affects very specific usage, but has a trivial workaround (priority)An edge case that only affects very specific usage, but has a trivial workaround (priority)feat: error pagesRelated to 404 and 500 handling (scope)Related to 404 and 500 handling (scope)feat: ssrRelated to SSR (scope)Related to SSR (scope)pkg: nodeRelated to Node adapter (scope)Related to Node adapter (scope)
Description
Metadata
Metadata
Assignees
Labels
- P2: has workaroundAn edge case that only affects very specific usage, but has a trivial workaround (priority)An edge case that only affects very specific usage, but has a trivial workaround (priority)feat: error pagesRelated to 404 and 500 handling (scope)Related to 404 and 500 handling (scope)feat: ssrRelated to SSR (scope)Related to SSR (scope)pkg: nodeRelated to Node adapter (scope)Related to Node adapter (scope)
What version of
astroare you using?2.10.3
Are you using an SSR adapter? If so, which one?
Node
What package manager are you using?
npm
What operating system are you using?
Mac
What browser are you using?
Chrome, Firefox, Safari
Describe the Bug
Have a page which returns 500 response.
Here is how behaviors differ:
What's the expected result?
Behavior of 500 response is consistent between modes, and content-type is returned correcly.
Link to Minimal Reproducible Example
https://stackblitz.com/edit/github-pt4enm-mla9j5
Participation