Darkie Minotaur

Resident
  • Content count

    1,663
  • Joined

  • Last visited

Community Reputation

157 Excellent

About Darkie Minotaur

  • Rank
    Advanced Member
  1. I usually use some kind of simple database on my outworld servers to which the inworld objects repoort their URLs whenever a restart, script restart ... occurs
  2. You should be a little more specific about what you want to do or achieve. I don't understand what you really mean.
  3. You can look at the examples - there is also one that uses php.
  4. Did you try with: $USE_APACHE_HEADERS = FALSE; ?
  5. I don't know what you used that didn't work - test is with TRUE - if that doesn't work, try FALSE
  6. Did you check the example "example wrapper script Both capturing apache headers and global methodes" here? I assume, this solves your problem.
  7. if you get a 404 error, there is something wrong with the URL. Does the request from the script get through? Another thing (which shouldn't be directly related to the 404 error) is that the if you send the parameters after the URL like you seem to do (i.e. starting with a ? after the URL), this will result in a GET request - whereas in the LSL script you use a POST request. I would think that the parameters that you type into the browser contain elements that result in a malformated URL. Let the LSL say the URL and the parameters - then copy and paste theser elements to the browser. This way you can make sure, they are encoded correctly. This should get rid of the 404 error - but it won't get you the result wanted, since you still have the GET vs. POST issue.
  8. Let me see if I get you right: you call an php from a browser - http://myserver.com/sample.php the call should include GET parameters like: http://myserver.com/sample.php?para1=1&para2=2 these parameters get passed by the php by CURL or fopen to a SL object that has a valid URL Where exactely does your problem with the character encoding happen?
  9. I do not fully understand, what you want to do in that test. If you send an URl from a browser, it gets encoded - I guess that's what you refer to when you're saying "not the correct format" - PHP usually handles that automatically.
  10. What you describe sounds sensible. Object in SL requests an URL LSL script in this object sends the URL to a web server where a PHP script stores the URL to some kind of DB (mySQL, text file) PHP retrieves the URL from the DB PHP sends a request to the object using tis URL Somewhere along this workflow, the URL sent to the PHP gets outdated - reasons could be: The DB contains old URLs e.g. the URL does not get updated, or an old URL doesn't get deleted ... The object gets rerezzed (e.g. because it gets tped) but the URL doesn't get updated. The object gets deleted without deleting the URL from the DB. Keeping the URLs of a complex system updated can get pretty painful.
  11. You can't. If I remember right, it's the uuid of the http-listener, as it where.Once the mapping is lost, the http-listener is lost
  12. Does the PHP script try to get the information to be passes back to the script that notifies you by means of http in? It seems to me that the messages you get is the message that SL sends you if http in gets an request for an outdated URL of an object.
  13. You just forgot the closing curly backets } on the second if statement
  14. Just to elaborate on what ObviousAltIsObvious said: The $_GET variable in PHP get populated by the key-value-pairs in the URL of a GET request. You put your values in the body of the HTTP-request, not in the URL, so the $_GET variable in PHP will be empty. The body is used in a POST request to pass the key-value-pairs.
  15. I find XML-RPC a bit sticky - it has never worked very stably for me. I usually use http-in to initiate a communication from a webserver to a scripted object. You have to make sure though that the SL object sends it's current URL to the webserver.