Jump to content

llHTTPrequest doesn't work beyond port 80


Recommended Posts

Up until yesterday, I was making great progress on a script that pulls shoutcast stream data from my shoutcast server using:
llHTTPRequest("http://my.shoutcast.server:8080/7.html",[],"");

Now suddenly it gets a timeout error.  I can still get that data from an external browser so I know the server on my end has not changed.  And in lsl I can still use llHTTPRequest on any address that's a regular port 80.  But any other port... not so much.  Has something changed in the way secondlife handles http requests that no longer accepts data from nonstandard ports?

If this is so, it pretty much kills every DJ venue on the grid that relies on that ability to display song titles.  And if I'm mistaken, tell me I'm an idiot and please show me what I'm doing wrong.  Thanks!

Link to comment
Share on other sites

Hi, in this other thread, notice the User-Agent hack appended to the URL --

 

HTTPRequest=llHTTPRequest(URL + "/7.html HTTP/1.0\nUser-Agent: LSL Script (Mozilla Compatible)\n\n",[],"");

 

Shoutcast relies on that "Mozilla" to know that it is supposed to send statistics. If it does not see it, it reverts to streaming mode and sends nothing good to LSL.

 

  • Like 2
Link to comment
Share on other sites

Thanks for the fast reply, Cerise. I understand about the Mozilla thing, but what threw me off was that it *just* stopped working today. Up until now, I think SL's default user-agent string included the word "Mozilla". But a quick test from my server reveals that it now sends: Second Life LSL/11.03.08.223047 (http://secondlife.com) ... unless you use the hack that you describe. Interestingly, I had exactly the same problem with OpenSim only in that case the hack doesn't work because the appended user agent string is stripped off before the URL is submitted.

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...