You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
riramar opened this issue
Mar 14, 2024
· 0 comments
· Fixed by #1669
Assignees
Labels
Status: CompletedNothing further to be done with this issue. Awaiting to be closed.Type: EnhancementMost issues will probably ask for additions or changes.
Add a flag to force HTTP1.1 only like --http1.1 on curl.
Describe the use case of this feature:
If the user wants to probe using HEAD method to speed up the process and filter/match responses by the Content-Length response header the tool must use HTTP1 because HTTP2 do not provides Content-Length response header.
The text was updated successfully, but these errors were encountered:
Status: CompletedNothing further to be done with this issue. Awaiting to be closed.Type: EnhancementMost issues will probably ask for additions or changes.
Please describe your feature request:
Add a flag to force HTTP1.1 only like --http1.1 on curl.
Describe the use case of this feature:
If the user wants to probe using HEAD method to speed up the process and filter/match responses by the Content-Length response header the tool must use HTTP1 because HTTP2 do not provides Content-Length response header.
The text was updated successfully, but these errors were encountered: