-
Notifications
You must be signed in to change notification settings - Fork 23
Raw Request Bug [304 Response = i/o timeout] #98
Copy link
Copy link
Closed
Labels
Status: CompletedNothing further to be done with this issue. Awaiting to be closed.Nothing further to be done with this issue. Awaiting to be closed.Type: BugInconsistencies or issues which will cause an issue or problem for users or implementors.Inconsistencies or issues which will cause an issue or problem for users or implementors.
Metadata
Metadata
Assignees
Labels
Status: CompletedNothing further to be done with this issue. Awaiting to be closed.Nothing further to be done with this issue. Awaiting to be closed.Type: BugInconsistencies or issues which will cause an issue or problem for users or implementors.Inconsistencies or issues which will cause an issue or problem for users or implementors.
Sorry, but the example with nuclei is easier for me
Nuclei version:
[INF] Current Version: 2.8.9
Current Behavior:
When sending an unprocessed request with a 'If-Modified-sinCe' header, no response is received and the request goes into a long timeout.
Expected Behavior:
An raw request must receive a valid response.
Steps To Reproduce:
Template:
Command:
we get exception could not read http body: read tcp
192.168.1.1:8080->198.248.233.148:443: i/o timeoutYou can remove unsafe: true from the yaml file to see the correct response.
OS: Windows 10, Ubuntu 18.04