hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HTTPCORE-475) Occasional issues in handling "204 No Content"
Date Sun, 02 Jul 2017 18:50:00 GMT

     [ https://issues.apache.org/jira/browse/HTTPCORE-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Oleg Kalnichevski resolved HTTPCORE-475.
----------------------------------------
    Resolution: Cannot Reproduce

I am not able to reproduce the issue locally. I really suspect that {{org.apache.http.NoHttpResponseException}}
may be genuine server condition when the origin server is unable to handler the request under
load. It does not look related to status 204.   

{noformat}
Reverse proxy to http://www.bing.com:80
Listening on port 8888
Incoming connection from /0:0:0:0:0:0:0:1
Outgoing connection to www.bing.com/204.79.197.200
Incoming connection from /0:0:0:0:0:0:0:1
New connection thread
>> Request URI: /
Outgoing connection to www.bing.com/204.79.197.200
New connection thread
Incoming connection from /0:0:0:0:0:0:0:1
Outgoing connection to www.bing.com/204.79.197.200
New connection thread
Incoming connection from /0:0:0:0:0:0:0:1
Outgoing connection to www.bing.com/204.79.197.200
New connection thread
Incoming connection from /0:0:0:0:0:0:0:1
<< Response: HTTP/1.1 200 OK
Outgoing connection to www.bing.com/204.79.197.200
New connection thread
Incoming connection from /0:0:0:0:0:0:0:1
Outgoing connection to www.bing.com/204.79.197.200
New connection thread
>> Request URI: /fd/ls/l?IG=C0C6506FCF9840E0B3E537EC328266A6&Type=Event.CPT&DATA={%22pp%22:{%22S%22:%22L%22,%22FC%22:-1,%22BC%22:-1,%22SE%22:-1,%22TC%22:-1,%22H%22:49,%22BP%22:52,%22CT%22:61,%22IL%22:1},%22ad%22:[-1,-1,1920,961,1920,961,0]}&P=SERP&DA=DB5
>> Request URI: /fd/ls/lsp.aspx?
<< Response: HTTP/1.1 204 OK
>> Request URI: /sa/8_01_0_000000/homepageImgViewer_c.js
<< Response: HTTP/1.1 204 OK
>> Request URI: /notifications/render?bnptrigger=%7B%22PartnerId%22%3A%22HomePage%22%2C%22IID%22%3A%22SERP.2000%22%2C%22Attributes%22%3A%7B%22RawRequestURL%22%3A%22%2F%22%7D%7D&IG=C0C6506FCF9840E0B3E537EC328266A6&IID=SERP.2000
>> Request URI: /sa/8_01_0_000000/HpbHeaderPopup.js
<< Response: HTTP/1.1 200 OK
>> Request URI: /HPImageArchive.aspx?format=js&idx=0&n=1&nc=1499020385089&pid=hp
<< Response: HTTP/1.1 200 OK
<< Response: HTTP/1.1 200 OK
>> Request URI: /fd/ls/l?IG=C0C6506FCF9840E0B3E537EC328266A6&Type=Event.PPT&DATA={%22S%22:40,%22E%22:270,%22T%22:0,%22I%22:0,%22N%22:{%22H%22:{%22S%22:119,%22E%22:258,%22T%22:1}},%22M%22:{}}&P=SERP&DA=DB5
<< Response: HTTP/1.1 200 OK
<< Response: HTTP/1.1 204 OK
>> Request URI: /fd/ls/lsp.aspx
<< Response: HTTP/1.1 204 OK
>> Request URI: /fd/ls/l?IG=C0C6506FCF9840E0B3E537EC328266A6&TYPE=Event.ClientInst&DATA=%5B%7B%22T%22%3A%22CI.Init%22%2C%22FID%22%3A%22CI%22%2C%22Name%22%3A%22Base%22%2C%22TS%22%3A1499020384985%7D%2C%7B%22Time%22%3A171%2C%22T%22%3A%22CI.Latency%22%2C%22FID%22%3A%22HP%22%2C%22Name%22%3A%22ImageStart%22%2C%22TS%22%3A1499020384985%7D%2C%7B%22Time%22%3A30%2C%22T%22%3A%22CI.Latency%22%2C%22FID%22%3A%22HP%22%2C%22Name%22%3A%22Image%22%2C%22TS%22%3A1499020385015%7D%5D
<< Response: HTTP/1.1 204 OK
>> Request URI: /fd/ls/lsp.aspx
<< Response: HTTP/1.1 204 OK
>> Request URI: /fd/ls/lsp.aspx
<< Response: HTTP/1.1 204 OK
>> Request URI: /fd/ls/lsp.aspx
<< Response: HTTP/1.1 204 OK
>> Request URI: /fd/ls/lsp.aspx
I/O error: Connection reset
Incoming connection from /0:0:0:0:0:0:0:1
Outgoing connection to www.bing.com/13.107.21.200
New connection thread
>> Request URI: /fd/ls/lsp.aspx
<< Response: HTTP/1.1 204 OK
Incoming connection from /0:0:0:0:0:0:0:1
>> Request URI: /fd/ls/lsp.aspx
Outgoing connection to www.bing.com/13.107.21.200
New connection thread
Incoming connection from /0:0:0:0:0:0:0:1
>> Request URI: /
Outgoing connection to www.bing.com/13.107.21.200
New connection thread
Incoming connection from /0:0:0:0:0:0:0:1
<< Response: HTTP/1.1 200 OK
Outgoing connection to www.bing.com/13.107.21.200
<< Response: HTTP/1.1 204 OK
Incoming connection from /0:0:0:0:0:0:0:1
New connection thread
Outgoing connection to www.bing.com/13.107.21.200
New connection thread
Incoming connection from /0:0:0:0:0:0:0:1
>> Request URI: /fd/s/a/hp/bing.svg
>> Request URI: /fd/ls/l?IG=A599E8C67BB84BDFBD168914BE42C239&Type=Event.CPT&DATA={%22pp%22:{%22S%22:%22L%22,%22FC%22:-1,%22BC%22:-1,%22SE%22:-1,%22TC%22:-1,%22H%22:36,%22BP%22:37,%22CT%22:69,%22IL%22:1},%22ad%22:[-1,-1,1920,961,1920,961,1]}&P=SERP&DA=DB5
>> Request URI: /fd/ls/lsp.aspx?
Outgoing connection to www.bing.com/13.107.21.200
New connection thread
<< Response: HTTP/1.1 200 OK
<< Response: HTTP/1.1 204 OK
>> Request URI: /notifications/render?bnptrigger=%7B%22PartnerId%22%3A%22HomePage%22%2C%22IID%22%3A%22SERP.2000%22%2C%22Attributes%22%3A%7B%22RawRequestURL%22%3A%22%2F%22%7D%7D&IG=A599E8C67BB84BDFBD168914BE42C239&IID=SERP.2000
>> Request URI: /sa/8_01_0_000000/HpbHeaderPopup.js
>> Request URI: /sa/8_01_0_000000/homepageImgViewer_c.js
<< Response: HTTP/1.1 204 OK
<< Response: HTTP/1.1 200 OK
<< Response: HTTP/1.1 200 OK
>> Request URI: /HPImageArchive.aspx?format=js&idx=0&n=1&nc=1499020491401&pid=hp
<< Response: HTTP/1.1 200 OK
Incoming connection from /0:0:0:0:0:0:0:1
Outgoing connection to www.bing.com/13.107.21.200
New connection thread
>> Request URI: /fd/ls/l?IG=A599E8C67BB84BDFBD168914BE42C239&Type=Event.PPT&DATA={%22S%22:30,%22E%22:241,%22T%22:0,%22I%22:0,%22N%22:{%22H%22:{%22S%22:116,%22E%22:237,%22T%22:2}},%22M%22:{}}&P=SERP&DA=DB5
<< Response: HTTP/1.1 200 OK
<< Response: HTTP/1.1 204 OK
>> Request URI: /fd/ls/lsp.aspx
<< Response: HTTP/1.1 204 OK
Incoming connection from /0:0:0:0:0:0:0:1
>> Request URI: /fd/ls/lsp.aspx
Outgoing connection to www.bing.com/13.107.21.200
New connection thread
Incoming connection from /0:0:0:0:0:0:0:1
>> Request URI: /
Outgoing connection to www.bing.com/13.107.21.200
New connection thread
Incoming connection from /0:0:0:0:0:0:0:1
<< Response: HTTP/1.1 204 OK
Outgoing connection to www.bing.com/13.107.21.200
New connection thread
Incoming connection from /0:0:0:0:0:0:0:1
<< Response: HTTP/1.1 200 OK
Outgoing connection to www.bing.com/13.107.21.200
New connection thread
Incoming connection from /0:0:0:0:0:0:0:1
Outgoing connection to www.bing.com/13.107.21.200
New connection thread
>> Request URI: /fd/s/a/hp/bing.svg
>> Request URI: /fd/ls/l?IG=A0D47D56A9A044D4B0E880096AA65EB9&Type=Event.CPT&DATA={%22pp%22:{%22S%22:%22L%22,%22FC%22:-1,%22BC%22:-1,%22SE%22:-1,%22TC%22:-1,%22H%22:48,%22BP%22:49,%22CT%22:70,%22IL%22:1},%22ad%22:[-1,-1,1920,961,1920,961,0]}&P=SERP&DA=DB5
>> Request URI: /fd/ls/lsp.aspx?
<< Response: HTTP/1.1 204 OK
>> Request URI: /notifications/render?bnptrigger=%7B%22PartnerId%22%3A%22HomePage%22%2C%22IID%22%3A%22SERP.2000%22%2C%22Attributes%22%3A%7B%22RawRequestURL%22%3A%22%2F%22%7D%7D&IG=A0D47D56A9A044D4B0E880096AA65EB9&IID=SERP.2000
>> Request URI: /sa/8_01_0_000000/HpbHeaderPopup.js
>> Request URI: /sa/8_01_0_000000/homepageImgViewer_c.js
<< Response: HTTP/1.1 200 OK
<< Response: HTTP/1.1 204 OK
<< Response: HTTP/1.1 200 OK
<< Response: HTTP/1.1 200 OK
<< Response: HTTP/1.1 200 OK
>> Request URI: /HPImageArchive.aspx?format=js&idx=0&n=1&nc=1499020493943&pid=hp
Incoming connection from /0:0:0:0:0:0:0:1
Outgoing connection to www.bing.com/13.107.21.200
New connection thread
>> Request URI: /fd/ls/l?IG=A0D47D56A9A044D4B0E880096AA65EB9&Type=Event.PPT&DATA={%22S%22:43,%22E%22:248,%22T%22:0,%22I%22:0,%22N%22:{%22H%22:{%22S%22:116,%22E%22:247,%22T%22:3}},%22M%22:{}}&P=SERP&DA=DB5
<< Response: HTTP/1.1 204 OK
<< Response: HTTP/1.1 200 OK
>> Request URI: /fd/ls/lsp.aspx
<< Response: HTTP/1.1 204 OK
{noformat}

> Occasional issues in handling "204 No Content"
> ----------------------------------------------
>
>                 Key: HTTPCORE-475
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-475
>             Project: HttpComponents HttpCore
>          Issue Type: Bug
>          Components: Examples, HttpCore
>    Affects Versions: 4.4.6
>         Environment: Windows, Java 8
>            Reporter: M.S. Dousti
>            Priority: Minor
>
> While testing {{ElementalReverseProxy}}, I noted that occasionally, some requests fail.
Digging further, it seems that the code has some difficulty in handling POST requests whose
responses have "204 No Content" status. The bug is intermittent, so it is a bit tricky to
reproduce. One way is to run the proxy against [http://www.bing.com]. (Notice it's HTTP and
not HTTPS). Here are the steps:
> 1) Change line 274 of {{ElementalReverseProxy}} to further assist in debugging, from:
> {code:java}
> System.err.println("I/O error: " + ex.getMessage());
> {code}
> to:
> {code:java}
> ex.printStackTrace(); System.exit(-1);
> {code}
> 2) Add the following lines to your {{hosts}} file ({{/etc/hosts}} in Linux, and {{%SystemRoot%\System32\drivers\etc\hosts}}
in Windows):
> {code:none}
> 127.0.0.1 bing.com
> 127.0.0.1 www.bing.com
> {code}
> 3) Run {{ElementalReverseProxy}} against one of Bing's IP addresses. I used {{204.79.197.200}}.
> 4) Navigate your browser to {{http://www.bing.com:8888}}, and watch the output of 
> {{ElementalReverseProxy}}. Here's a sample run:
> {code:none}
> Listening on port 8888
> Incoming connection from /127.0.0.1
> Outgoing connection to /204.79.197.200
> New connection thread
> >> Request URI: /
> << Response: HTTP/1.1 200 OK
> Incoming connection from /127.0.0.1
> Outgoing connection to /204.79.197.200
> Incoming connection from /127.0.0.1
> New connection thread
> >> Request URI: /fd/ls/l?IG=3C1FD9BC348B419DAF07D5D09D135555&CID=3ED5D1926AB96D71082FDB206BCB6CA6&Type=Event.CPT&DATA={%22pp%22:{%22S%22:%22L%22,%22FC%22:-1,%22BC%22:-1,%22SE%22:-1,%22TC%22:-1,%22H%22:116,%22BP%22:134,%22CT%22:169,%22IL%22:1},%22ad%22:[-1,-1,1600,770,1600,770,0]}&P=SERP&DA=Bn2
> Outgoing connection to /204.79.197.200
> New connection thread
> >> Request URI: /fd/ls/lsp.aspx?
> Incoming connection from /127.0.0.1
> Outgoing connection to /204.79.197.200
> New connection thread
> Incoming connection from /127.0.0.1
> >> Request URI: /notifications/render?bnptrigger=%7B%22PartnerId%22%3A%22HomePage%22%2C%22IID%22%3A%22SERP.2000%22%2C%22Attributes%22%3A%7B%22RawRequestURL%22%3A%22%2F%22%7D%7D&IG=3C1FD9BC348B419DAF07D5D09D135555&IID=SERP.2000
> Outgoing connection to /204.79.197.200
> New connection thread
> Incoming connection from /127.0.0.1
> >> Request URI: /sa/8_01_0_000000/HpbHeaderPopup.js
> << Response: HTTP/1.1 204 OK
> Outgoing connection to /204.79.197.200
> New connection thread
> >> Request URI: /sa/8_01_0_000000/homepageImgViewer_c.js
> << Response: HTTP/1.1 200 OK
> << Response: HTTP/1.1 200 OK
> << Response: HTTP/1.1 200 OK
> >> Request URI: /HPImageArchive.aspx?format=js&idx=0&n=1&nc=1498898493932&pid=hp
> org.apache.http.NoHttpResponseException: The target server failed to respondIncoming
connection from /127.0.0.1
>         at org.apache.http.impl.io.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:131)
>         at org.apache.http.impl.io.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:53)
>         at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:259)
>         at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:163)
>         at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:273)
>         at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
>         at ElementalReverseProxy$ProxyHandler.handle(ElementalReverseProxy.java:134)
>         at org.apache.http.protocol.HttpService.doService(HttpService.java:437)
>         at org.apache.http.protocol.HttpService.handleRequest(HttpService.java:342)
>         at ElementalReverseProxy$ProxyThread.run(ElementalReverseProxy.java:262)
> {code}
> I don't know whether the problem lies within {{ElementalReverseProxy}}, or the way HC
handles the requests/responses.
> I also wrote a simple PHP/HTML/JavaScript to reproduce the error without relying on Bing,
which I can provide if needed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


Mime
View raw message