Hi Guys,
Thanks for the suggestions.
It seems that upgrade in this case uses what one of my friends (who works in
product management for a software vendor) describes as a bumpy upgrade path
with limited appeal to the customer i.e. no backward compatibility ;-)
I am currently reading through
On Mon, 2011-02-07 at 10:28 +0100, khiem nguyen wrote:
Hi,
i'm trying to use httpclient 4.1 to get some stream-content from this site
http://oe1.orf.at/konsole/?show=live
this doesnt work, log message:
DefaultResponseParser [DEBUG] Garbage in response:
from browser, debug with firebug
On Mon, 2011-02-07 at 10:01 +, ewan.sla...@googlemail.com wrote:
Hi Guys,
Thanks for the suggestions.
It seems that upgrade in this case uses what one of my friends (who works in
product management for a software vendor) describes as a bumpy upgrade path
with limited appeal to the
On 7 February 2011 10:01, ewan.sla...@googlemail.com wrote:
Hi Guys,
Thanks for the suggestions.
It seems that upgrade in this case uses what one of my friends (who works in
product management for a software vendor) describes as a bumpy upgrade path
with limited appeal to the customer
here's logging-console:
DEBUG [org.apache.http.impl.conn.tsccm.ThreadSafeClientConnManager] Get
connection: HttpRoute[{}-http://mp3stream3.apasf.apa.at:8000], timeout =
3
DEBUG [org.apache.http.impl.conn.tsccm.ConnPoolByRoute] [HttpRoute[{}-
http://mp3stream3.apasf.apa.at:8000]] total kept
On Mon, 2011-02-07 at 13:58 +0100, khiem nguyen wrote:
here's logging-console:
...
DEBUG [org.apache.http.wire] ICY 200 OK[\r][\n]
DEBUG [org.apache.http.impl.conn.DefaultResponseParser] Garbage in response:
ICY 200 OK
'ICY 200 OK' is not a valid HTTP status line.
Oleg
ok, i see
so the server gives junk status-header back to the client.
is there a way to overcome this ?, i mean how can i replace
the DefaultResponseParser without touching the client's code too much ( just
like a responseInterceptor ???), i guess there'll be many other websites
which doing
