• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: SVC-4109
Type: Bug Bug
Status: Open Open
Priority: Normal Normal
Assignee: Unassigned
Reporter: Xugu Madison
Votes: 6
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
2. Second Life Service - SVC

llLoadURL() maximum URL length problematic with http-in

Created: 12/Apr/09 12:04 PM   Updated: 01/Oct/09 04:53 PM
Return to search
Component/s: LSL HTTP, Scripts
Affects Version/s: None
Fix Version/s: None

File Attachments: 1. Text File url_length_test.lsl.txt (1 kB)

Issue Links:
Relates
 


 Description  « Hide
llLoadURL() truncates URLs at 255 characters, which is a problem in use cases such as passing an http-in URL to a remote system through use of llLoadURL for callback usage.

URLs passed back by http-in are around 81 characters, and 107 characters once URL-encoded. Assuming another 80-ish characters for the basic URL of the target system, this leaves 70-ish characters for any other data being passed through the URL, which isn't that hard to exhaust (particular if, for example, you're passing an avatar key in the URL as well).

Could we please have an increased acceptable length for llLoadURL() to resolve this? Unless you have any actual proven security or performance issues, I'd suggest uncapping the URLs (and leaving LSL memory requirements to act as a sanity check).

I've attached a simple LSL script which grabs an http-in URL and shows it, plus it's URL-encoded equivalent, along with lengths.



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Strife Onizuka added a comment - 08/Jul/09 09:09 AM
making the length 511 or 1023 would be more reasonable. I think Firefox has it's URL length limit set to 4k.

ellen spark added a comment - 26/Jul/09 12:36 PM - edited
Yes, I totally agree with this issue, I have the same prolbem due th the trunucation of url addresses.
The trunucateing of the addersses has a very negitive impact on improveing SL commerece.
Some long address strings are needed to supply commerece data to the site you wish to
have people access as we all well know. Please give us a fix for this issue.

Thanks,
Ellen


alice klinger added a comment - 27/Jul/09 11:00 PM
Ohh nice idea to give the 4000 chars instead of the current 255! Please make this happen, I can see great improvement options for SL commerce here as well!

Cinco Pizzicato added a comment - 01/Oct/09 04:53 PM
1k sounds good to me.

Here's my suggestion for bare-minimum inter-object handshake protocol of some type:

http://your.prim.url/command/urlencodedUUID/urlencodedreturnURL/

No way that will fit in 255.

The work-around is to POST some kind of silly non-standard file with the return URL in it. This works but is completely inelegant and requires that we violate http standards right off the bat, just to get a handshake going. And the only reason we do that is because of this arbitrary limitation.