-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Sveltekit demo project deployed to Heroku gives HTTP 416, when using Linkedin Post Inspector #9549
Comments
Does it work for non-pre-rendered routes? Could you log from one of them what exactly the incoming request from LinkedIn looks like? The 416 makes me think they are sending some wacky |
Yes, it works for non-pre-rendered routes. You can check here. The post inspector shows the following headers:
Must be the |
Is it possible to maybe give this issue some attention/high priority? Just to clarify: Sveltekit just doesn't support link previews by Linkedin on pre-rendered pages 😱 |
Would it be too much to ask, if we can throw in a bug label and some priority label @dummdidumm? Did spend a lot of time making sure this was something that could be reproduced, and I'm keeping the Heroku app running until we have a fix. |
@alexbjorlig thanks for the investigation. It seems unlikely this bug is in SvelteKit itself, but more likely it's in one of the libraries we use like An idea for figuring out whether it's Actually, now that I think about it, since it only happens with prerendered pages, probably it's |
According to this, it sounds like a 416 should only be returned if the start is out of bounds and the server should return the available overlap with the requested range even if the end is out of bounds. Whereas sirv returns a 416 if either ends of the requested range are out of bounds. There is an issue and PR open in sirv for this: lukeed/sirv#140 |
Did you mean to write?
|
No. Prerendered pages are static. |
Ok - I'm sorry I don't completely understand it then. I hope we have a fix quickly - currently, the node-adapter does not support building a project with pre-rendering and linking to it on Linkedin 😱 |
this has been fixed in |
@benmccann |
Describe the bug
Prerendered pages deployed to Heroku with the
@sveltejs/adapter-node
gives 416 error:Reproduction
To reproduce this issue, I created this repo.
it's deployed to this Heroku app.
Try to use the LinkedIn post inspector for the about pre-rendered route, and you get the HTTP 416 error.
Logs
Severity
blocking an upgrade
Additional Information
No response
The text was updated successfully, but these errors were encountered: