|
Chance Unknown
Registered User
Join date: 17 Feb 2006
Posts: 18
|
07-25-2006 22:22
I propose adding an extension to the llHTTPRequest() function in order to supply additional header elements as part of the request. Specifically, some sites require basic authentication tokens in order for the URL to be processed. It would be nice to be able to add these header elements in the HTTP request so a scripted object can access external websites that have authentication requirements. Also, it could be useful to insert additional header elements as required with other sites.
llHTTPRequest(url, [ HTTP_METHOD, "POST", HTTP_HEADER, [ "Authentication", token_string ], ......
|
|
Ben Fassbinder
Registered User
Join date: 16 Jun 2005
Posts: 13
|
I have created a proposal for this in the feature voting system
12-04-2006 20:46
|
|
SpaceQ Isan
Registered User
Join date: 20 Oct 2006
Posts: 22
|
Iam against
12-05-2006 04:49
This would add weak plaintext authentication from last century into sim. If you want implement authentication POST + 2 key system via your web server and then redirect to any old web sites.
|
|
Ben Fassbinder
Registered User
Join date: 16 Jun 2005
Posts: 13
|
12-05-2006 15:19
From: SpaceQ Isan This would add weak plaintext authentication from last century into sim. If you want implement authentication POST + 2 key system via your web server and then redirect to any old web sites. Yes, if you are sending e.g. a password in a plaintext header. Your solution of redirecting through an auxillary webserver adds unnecessary complexity, though, for simple cases where one simply needs to get the job done and security is not a priority. I don't want to have to run my own webserver or hire a hosting company just for this single trivial purpose. Besides, there are many other uses for custom http headers that cannot currently be employed due to this feature not existing. Also, in situations where the security of the information is required, doesn't SSL protect the headers as much as the payload. The llHTTPRequest() function does support https protocol. But, I'm no expert on HTTP, so I could be wrong. But from my perspective, if LSL is going to include HTTP it seems a shame to leave out an integral part of the standard, particularly when that oversight greatly increases the complexity of getting simple jobs done.
|