Difference between revisions of "Talk:LlHTTPRequest"
(Odd format for header names) |
Anylyn Hax (talk | contribs) |
||
Line 1: | Line 1: | ||
I have a Question .. | |||
Does POST work ? | |||
I couldnt get it working | |||
Anylyn Hax 13:34, 28 July 2007 (PDT) | |||
The following headers will be present, usable by scripts running on the HTTP server if the scripting language allows you to access the headers. | The following headers will be present, usable by scripts running on the HTTP server if the scripting language allows you to access the headers. | ||
Revision as of 12:34, 28 July 2007
I have a Question .. Does POST work ? I couldnt get it working Anylyn Hax 13:34, 28 July 2007 (PDT)
The following headers will be present, usable by scripts running on the HTTP server if the scripting language allows you to access the headers.
An PHP example on how to check to see if the call came from the main grid:
<?php if ($_SERVER["HTTP_X_SECONDLIFE_SHARD"] == "Production") { echo 'You are using the main grid'; } else { echo 'You are not using the main grid'; } ?>
Odd format for header names
Why are the headers listed as HTTP_SOME_HEADER_NAME, when the sent headers are in the format Some-Header-Name? Is there some benefit to putting false values that match conventions used by CGI, but aren't actually correct?
I am aware that the example given above works, but (assuming that you're using mod_php) this would too, and reflects the real header names:
<?php $headers = apache_request_headers(); if($headers['X-SecondLife-Shard'] == 'Production') { print "You are on the main grid."; } else { print "You are on a preview grid."; } ?>
Additionally, the current information does not show the capitalisation, thus further confusing the matter. Katharine Berry 09:55, 21 June 2007 (PDT)