Jump to content

Shuichi Shinji

Resident
 View Profile  See their activity

  • Posts

    63

  • Joined

  • Last visited

 Content Type 

Everything posted by Shuichi Shinji

  1. Shuichi Shinji
    I did some tests and Shoutcast v1 servers seemed ok so far which is good news :-) Icecast using the HTML status page also seems to work, the one using a JSON status page still needs to be tested (I didn't find one anymore), but that one should also be ok, I guess. I do have an issue with at least one Shoutcast v2 stream: http://stardust.wavestreamer.com:8062 Checking in the browser is ok and also the XML status page http://stardust.wavestreamer.com:8062/stats?sid=1 which my script parses, but I only get a 403 error with no further information in the script. Another Shoutcast v2 stream (http://www.ebm-radio.org:7000/) is working fine, though. And I found a stream (http://74.208.197.50:8087/) which seems to offer Shoutcast v1 and v2 and it also replies with a 403 error while in the browser, v1 and v2 status pages work. They are all working with the old server and script version.
  2. Shuichi Shinji
    The example change Oz provided, included a "/1.0" after the user agent name (before the parentheses), I guess it's important. Your second try with the "\n\n" is definitely wrong, but the first should work with the added "/1.0" in my opinion.
  3. Shuichi Shinji
    Ok, I do understand that and if you have other steps in mind that are better, I'm all for it :-) The script I am selling supports Shoutcast v1+2 and Icecast, so I will test them all once the new server version is rolled out and I have the time to do it, also with different URLs and I will report any issues. I did have problems with Icecast too when this started, so those servers might be affected too, unless it was another, unrelated issue.
  4. Shuichi Shinji
    Yes, I read the other post and it's good that it mostly works again, but my suggestion was specifically about "not updated" scripts, and while I personally don't care so much about SHX, I know many use it and need to buy something else now (good for other creators like me, bad for customers). But I understand (and agree) it's not a good idea and would be just a messy workaround, so I guess SHX users just have to swallow the pill... Still, "most servers" is a bit unsatisfying since we don't have much influence on their configuration. So I would be interested to know whether my other suggestion about an option HTTP_SKIP_DEFAULT_HEADERS or similar which would give scripters more control over the headers being sent would be considered a better idea, maybe in a later update. Thank you :-)
  5. Shuichi Shinji
    And another question: Would it be possible to parse the hack (in a very restrictive way to avoid security issues) and build a standard-conforming HTTP request out of it? That would have the advantage that old scripts incl. SHX would still work. The preferred way would of course be the one using the extra options for user agent and potentially to skip the default headers, but to not break old content, the hack parsing would really be helpful...
  6. Shuichi Shinji
    @Oz: Thank you for explaining the issue in such detail, it really helps understanding the difficulties in resolving this in a sensible way... Would be be a possible solution to add another option to llHTTPRequest like HTTP_SKIP_DEFAULT_HEADERS or HTTP_SKIP_SL_HEADERS so the user of the command can decide whether or not to send the X-SecondLife headers?
  7. Shuichi Shinji
    I see, thank you for the info.
  8. Shuichi Shinji
    Okay, I had 17.06.12.327111 (if I remember correctly; this version is not listed in http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_Magnum/17#17.06.12.327060) and the fix seems to be in since 17.06.12.327060 according to that page.
  9. Shuichi Shinji
    What is the server version on that region? Maybe it didn't get the new version yet for whatever reason...
  10. Shuichi Shinji
    I could get it to compile yesterday on a Magnum region and only got that error on other regions, as expected. So the parameter does exist there, but it still doesn't work, sadly. I didn't check the server response, but it's probably the same issue Qwalyphi Korpov described.
  11. Shuichi Shinji
    Thank you, Oz!
  12. Shuichi Shinji
    Thank you, Oz :-)
  13. Shuichi Shinji
    Could you please provide some details about the issue, please? It also affects other scripts, including my own, so it would be good to know how to fix it. I can also provide the script if necessary. Thank you ^^
×
×
  • Create New...