Icecast - May 2018 - EROR connection/_handle_connection Wrong request type > from client

Thanks for clarifying that Philipp.

Yeah, I compared the time stamps in the error.log and access.log (below)
and saw the corresponding HEAD requests. I've been getting a lot of
these so I thought that there was something I could do to allow these
clients to connect to the stream. I guess I just need to ignore them.

Thanks
Damian



Snippet from error.log
[2018-05-04  00:28:17] EROR connection/_handle_connection Wrong request
type from client
[2018-05-04  00:28:17] EROR connection/_handle_connection Wrong request
type from client

Snippet for access log
158.69.38.195 - - [04/May/2018:00:28:17 +1000] "HEAD /Systrum
HTTP/1.1"
400 336 "-" "curl/7.29.0" 0
158.69.38.195 - - [04/May/2018:00:28:17 +1000] "HEAD /Systrum
HTTP/1.1"
400 336 "-" "curl/7.29.0" 0

> 
> This is correct. Some listen clients try a HEAD request first (most of
> no good reason). You can also see the requests in your access log.
> 
> Look for lines like this:
> 
> 127.0.0.1 - - [02/May/2018:12:17:08 +0000] "HEAD / HTTP/1.1" 400
430
> "-" "Wget/1.18 (linux-gnu)" 0
>

Good morning,

On Thu, 2018-05-03 at 18:11 -0700, Damian wrote:
> Thanks for clarifying that Philipp.
> 
> Yeah, I compared the time stamps in the error.log and access.log (below)
> and saw the corresponding HEAD requests. I've been getting a lot of
> these so I thought that there was something I could do to allow these
> clients to connect to the stream.
The HEAD requests are basically: Hello, what are you?
They would not result in a connect to the stream anyway, the answer
would just be 'Audio/Video data!'.

I also think that for playing media streams they add more trouble than
they are worth (Hint to developers: They only add race conditions.)
> I guess I just need to ignore them.
Yes. That's the only option you have as a server operator.

I'm glad my answerer helped you.

With best regards,

> Snippet from error.log
> [2018-05-04  00:28:17] EROR connection/_handle_connection Wrong request
> type from client
> [2018-05-04  00:28:17] EROR connection/_handle_connection Wrong request
> type from client
> 
> Snippet for access log
> 158.69.38.195 - - [04/May/2018:00:28:17 +1000] "HEAD /Systrum
HTTP/1.1"
> 400 336 "-" "curl/7.29.0" 0
> 158.69.38.195 - - [04/May/2018:00:28:17 +1000] "HEAD /Systrum
HTTP/1.1"
> 400 336 "-" "curl/7.29.0" 0
> 
> 
> > 
> > This is correct. Some listen clients try a HEAD request first (most of
> > no good reason). You can also see the requests in your access log.
> > 
> > Look for lines like this:
> > 
> > 127.0.0.1 - - [02/May/2018:12:17:08 +0000] "HEAD / HTTP/1.1"
400 430
> > "-" "Wget/1.18 (linux-gnu)" 0

-- 
Philipp Schafft (CEO/Geschäftsführer) 
Telephon: +49.3535 490 17 92

Löwenfelsen UG (haftungsbeschränkt)     Registration number:
Bickinger Straße 21                     HRB 12308 CB
04916 Herzberg (Elster)                 VATIN/USt-ID:
Germany                                 DE305133015
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part
URL:
<http://lists.xiph.org/pipermail/icecast/attachments/20180504/1a710c45/attachment.sig>