Displaying 2 results from an estimated 2 matches for "dump_sourc".
Did you mean:
dump_source
2009 Feb 05
2
m3u generation prefers one TCP port
I have auto-generated m3u's preferring port :8000 even when accessed
from :80
<listen-socket>
<port>8000</port>
</listen-socket>
<listen-socket>
<port>80</port>
</listen-socket>
~% w3m -dump_source http://icecast.playlouder.com:80/totalrock.m3u
http://icecast.playlouder.com:8000/totalrock
~%
Is this a bug or misinterpretation of the config?
C.
--
020 7729 4797
http://blog.playlouder.com/
2009 Feb 05
0
m3u generation prefers one TCP port
...m3u's preferring port :8000 even when accessed
> from :80
>
> <listen-socket>
> <port>8000</port>
> </listen-socket>
> <listen-socket>
> <port>80</port>
> </listen-socket>
>
> ~% w3m -dump_source http://icecast.playlouder.com:80/totalrock.m3u
> http://icecast.playlouder.com:8000/totalrock
> ~%
>
> Is this a bug or misinterpretation of the config?
The automatic m3u generation uses the Host: header if available and
falls back to the <hostname> and first port defined whe...