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

"Range request exceeds file boundaries" in console #212

Open
Zarel opened this issue Oct 4, 2018 · 2 comments
Open

"Range request exceeds file boundaries" in console #212

Zarel opened this issue Oct 4, 2018 · 2 comments

Comments

@Zarel
Copy link

Zarel commented Oct 4, 2018

I got some errors in my console:

Range request exceeds file boundaries, goes until byte no 32768 against file size of 450 bytes
Error: Range request present but invalid, might serve whole file instead

Looks like either someone's trying to probe me for vulns, or someone's HTTP client is buggy. But why is this output to my error console? It seems like this should either be a 400 status code, or just ignored entirely. There should at least be some setting to turn it off, so my console can be reserved for server-side errors rather than client-side errors.

@sammyt291
Copy link

sammyt291 commented Mar 17, 2020

I can replicate this by linking to a node-static served page under 524287bytes in facebook messenger.

Range request exceeds file boundaries, goes until byte no 524287 against file size of 203 bytes

The range request on facebook messenger is it trying to generate a preview for the link if possible.

"Might serve file instead", why might? can we force it to?
And if so, what are the implications?

@andrewhodel
Copy link

This is the same issue as #185.

This is about standard output and standard error, as it is consistently request-able from any HTTP client to any HTTP server using node-static, it should not be printed to standard output or standard error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants