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

Support for storing response header only #32

Open
ehsandeep opened this issue Nov 3, 2018 · 1 comment
Open

Support for storing response header only #32

ehsandeep opened this issue Nov 3, 2018 · 1 comment

Comments

@ehsandeep
Copy link

Hi @tomnomnom,

Right now meg store response body for all the request, but sometimes we only look for response header for some header inspection, and we have no option to store the only header or exclude the body, will suggest to have optional flag for the same, as It can improve the speed in case we are only looking for response header.

@leesoh
Copy link
Contributor

leesoh commented Oct 1, 2019

I think this feature will definitely save a bit of space, but I'm not so sure about saving time since the GET metho retrieves:

whatever information (in the form of an
entity) is identified by the Request-URI.

Taken from RFC 2616. If you scroll down a page on that RFC though, you'll run into the HEAD request, which:

is identical to GET except that the server MUST NOT
return a message-body in the response.

AND, a web server must support both GET and HEAD; all other methods are optional.

Does meg -X HEAD work for you?

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

2 participants