-
Notifications
You must be signed in to change notification settings - Fork 270
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
Display Human-readable size of the http response #25
Comments
Hello! That's a thought. I think that would be useful, but I don't want to go too far in to adding features all in one tool. It is a bit of a pain to find real 200 OK responses though for the reason you mention. I'll give it some thought and get back to you :) |
Most of the analysis I do on the output files is done with standard linux tools, so I haven't really thought so much about this kind of thing yet. To tide you over, here's a bit of bash that will list the files, the address, and the size of the file in bytes:
And here's what I might do if I was looking for only '200 OK' responses:
|
Hi @tomnomnom, Any development on this for inbuild support? displaying content length along with status code at runtime? |
Hi @MadaraTech , We can get the length/size of the response by using Just change this line in your code and then compile it. Hope it helps :) |
Could you show the length of the response in output?
Some sites don't care about best practices and responds with 200 status code to show their custom 404 pages ("sorry not found"), making it hard to detect positive findings.
With size in output we can easily filter out those findings...
The text was updated successfully, but these errors were encountered: