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/
Charlie Allom wrote:> 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?The automatic m3u generation uses the Host: header if available and falls back to the <hostname> and first port defined when not. karl.
On Thu, Feb 05, 2009 at 03:00:09PM +0000, Karl Heyes wrote:> Charlie Allom wrote: >> 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? > > The automatic m3u generation uses the Host: header if available and > falls back to the <hostname> and first port defined when not.Thanks - I will kill && start it later today to get this working! C. -- 020 7729 4797 http://blog.playlouder.com/