07-25-2012 03:23 AM
In our application we need to receive an xml data from our server, We using BIS connection, When we receiving the data we got "HTTP error 413 request entity too large" . While seraching we got this is the problem of large size of data, We are using BIS connection, Is there any way to receive the large sized data ?
07-25-2012 04:22 AM
Two immeidate thoughts.
a) Use Wifi for this download
b) Use this approach, whihc applies to BIS-B as well:
07-25-2012 04:40 AM
Thanks for your quick reply.
In our existing application we send the xml data as packets, Now we are trying to improve the performance , for this we need to send the entire data as one packet, so the size of the packet will increase and got the error "HTTP 413 - Request Entity Too Large " . We cannot say all our clients to use WiFi,
have you any other thoughts ?
07-25-2012 04:54 AM
I appreciate not everyone has WiFi, but it is worth the effort to detect this and use WiFi for the download since it could be a lot faster.
If you are not using WiFi, I think the chunking will not have that much impact on the overall time, and more importantly, if there is a problem you can recover from just the failed chunk. I suggest that you test this approach compared with downloading it in one hit.
Another option is to use a different communication method. As far as I know, neither WAP nor Carrier TCP have these limits on the size, however on some carrier plans these cost - your users may not appreciate being charged just so that they can download quicker. But then again, they might not mind and they might not be changed.
What size data are we talking here?
07-25-2012 08:57 AM
Not sure maximum, but I thought it was higher than you are seeing:
Just realized of course that you might not be using BIS-B, so you might be suffering a limit imposed by your carrier. What connection method are you using - BIS-B, WAP, Carrier TCP? if you are using WAP or Carrier TCP, then the limit is possibly something you can't do anything about.....
07-25-2012 09:36 AM - edited 07-25-2012 09:50 AM
Now we append the url with ";deviceside=false;ConnectionType=mds-publc" for BIS
Which string we should append for BIS-B ?
We got the same error "requested entity too large" in the simulator, we using the following code for the simulator
url = url.concat(";deviceside=false");