Limit on http_response's body?

I did a printout of the body, and with limit of 2KB, which isn't even past the metadata part!!

Why would they create a function and then put a non-sense limitation on it? This is great server technology!?

After saving the content in hdd, it turn out there's just 1049KB, so where's the other 1000KB?

From what i know that's the limit unfortunately. However you could simply overcome this by putting up a simple php script somewhere in other web storage. Use a LSL script to call up the php script, it will then find anything information you need from webpage, parse string, characters etc., then send the data you want back to the LSL script. There's no limitation on the php script.

The limit is in bytes, not characters. And I believe it is on the whole message, not just the body. It is really meant for small application API communication, not grabbing whole web pages or anything.

But yeah, I agree. It bytes. It'd be nice if it were at least 4-8 times that big. Really nice.

A web page that's over 1MB? That really needs to be split up. Apart from any LSL limitations you may have trouble depending on any of the hubs/switches/routers between the data-source and SL. Quite simply, they are not 'required' to pass that much data in one go. Something that size should be 'chunked', streamed or simply put on different pages.

Having issues with this myself. I am trying to call a bit of info that is far down on the page source. Its a small page and its just to far from the start or end to get to it from either direction.

Thanks guys for replies,

Guess i will have to write a jsp instead to grasp what I want from the page...

but 2KB, no wonder some ppl laughs at SL... why bother!?

They don't have to, HTTP works over TCP, which splits the data into MTU-size packets.