OmniCron Overlord
Registered User
Join date: 28 Nov 2005
Posts: 31
|
05-21-2006 11:58
Before the db crash i was able to return about 2000 characters from the HTTPResponse in the body parameter. The Wiki says this is still true. HOWEVER currently I am being truncated to 512. I have tested the script on the server that returns the data and it is returning more than the 512. I have even used curl to simulate the LSL request and get back the whole dataset. This change cuts the limit down to a quarter of the original size. Is this permanent or am i likely doing something incorrectly?
|
Torley Linden
Enlightenment!
Join date: 15 Sep 2004
Posts: 16,530
|
05-21-2006 23:09
Asking about this...
|
Zero Linden
Linden Lab Employee
Join date: 18 Oct 2005
Posts: 22
|
05-22-2006 10:33
The scoop:
Actually, nothing has changed, this bug was there all along! If the response has newlines at least every 512 bytes, it will work, and return you up to 2048 bytes worth of response. The bug is that if there are no newlines, then it accidentally only sees the first 512 bytes.
This should be fixed in the next deploy. (Compiling the test as I type...)
Note: The limits are in terms of bytes. However, due to both transcoding (from what ever character set the response was in), and newline normalization (all newline types are converted to just single '\n' characters), the number of characters in the response might be different than the byte count.
|