-
Notifications
You must be signed in to change notification settings - Fork 28
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
McAfee Integration: Status Code 418 #14
Comments
Hi, I updated the request to specify an empty request header ie I'm now getting an IOException Connection reset by peer: socket write error I'll investigate to see if this is an issue on the server. Thanks, |
I've never had access to an McAfee server, so I don't know if my code is compatible. The "GET ..." part from #8 would be the encapsulated HTTP request, but it seems confusing, when you cannot differentiate what the server and client says. My code will be sending the file inside the datastream. So I cannot say for sure why the filepath is in the request. If you find a solution, I will gladly update my code accordingly. |
If this issue still occurs, you may try with the latest code, perhaps can work with it. |
i have tired latest code but yet getting Server returned unknown status code:418 Content-Length: 696416 1E\r\n" |
Hi,
When trying to implement with a McAfee server, I am recieving error code 418 which I believe means my request is missing a required request header.
I read the issue raised by sc06 and followed their advice (#8 (comment)) modifying the request as follows:
ESPMOD icap://<I.P.>/RESPMOD ICAP/1.0
Host: <I.P.>
X-Client-Abandon-Supported: 1
Preview: 30
X-Scan-Progress-Interval: 10
Allow: 204
Encapsulated: res-hdr=0, res-body=26
Content-Length: 572939
1e
I dont understand how sc06 created a request header.
Is the following from their comment the request header?:
"GET /C:\TestFiles\test1.txt HTTP/1.1
Host: icap.health.check"
Why would that need to be sent? Do I need to make the file available on that host?
Please forgive my lack of knowledge around the protocol.
Thanks very much for your help.
Charlie.
The text was updated successfully, but these errors were encountered: