| ResponseSizeLimits =Yes/No |  Search
|
|
NowSMS Support Forums ⬆ Now.WAP Proxy Support ⬆ Archive through September 22, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Rodionov Sergey Unregistered guest |
Pls clear this setting, 'cause the documentation page's topic is very unclear... What value should I use for this setting if I DO NOT WANT a control a size of a traffic. What is a default value. Thax in advance. | |||
| Kent Williams Moderator Username: Kent Post Number: 65 Registered: 10-2003 |
Hi, ResponseSizeLimits=No is the setting that you would want to use. That is the default setting. However, I just did some checking, and it appears that this setting is not working properly in the current version. In the current version, this setting is defaulting to ResponseSizeLimits=Yes, and the configuration option to disable this setting is not working. If you send an e-mail message to wap@now.co.uk, I can send you an update that fixes this problem. Please note, ResponseSizeLimits=Yes should not cause any problems with properly written browser implementations. The browser specifies what the maximum size of the data it can accept is at the time of connection. If the data to be returned exceeds that size, this is when we would return a response size error. If ResponseSizeLimits=No, then we ignore the limit, and try to send it anyway. If you are encountering an unexpected size limitation, it is possible that you are connecting using the "connection-less" WAP protocol. The "connection-less" WAP protocol does not support any segmentation-and-reassembly, and we will limit any downloads over this protocol to 16KB, regardless of the above setting. (Large data transfer over UDP without segmentation and re-assembly is not a good idea.) Most WAP devices have two options for how to configure the connection to the proxy. There is the "connection-less" protocol (referred to as "temporary" on some phones, or "port 9200" on some other phones) or the "connection-oriented" protocol (referred to as "permanent" on some phones or "port 9201" on some other phones). I recommend that you ALWAYS use the "connection-oriented" protocol. Most of the time when someone is running into unexpected response size limits, the issue is whether they are using connection-oriented or connection-less protocol. That is probably why we had not noticed that this particular setting was broken. But if you do need an update to properly set ResponseSizeLimits=No (actually that setting will be fixed to be default again), then please e-mail wap@now.co.uk, and I will e-mail the update to you. (And the web site should be updated with a new download within a few days.) -- Kent Williams Now Wireless Support | |||
| Anonymous |
Hi Kent! I'm developing a J2ME application which has to communicate over HTTP (on a Nokia series 40 phone which uses a WAP stack). Could you explain a little more how "The browser specifies what the maximum size of the data it can accept at the time of connection". I want to receive a large message on the phone (more than 100k) but from the gateway I get the message "<...>Page is too large to send back." How can I say in the request that I make from the browser(phone) that I want to be able to receive a larger message. At least a link, a clue, something to look for. (I've lookled over HTTP headers and have't found anything). Thanks! | |||
| Kent Williams Moderator Username: Kent Post Number: 93 Registered: 10-2003 |
When the browser connects to a WAP gateway, it indicates the maximum size supported by its WAP stack. This is part of the WSP connect primitive, which is the first message sent by a client to initiate a session. You can enable the debug log in Now.WAP, and it will tell you what the max size is that the phone has requested. Edit WAPGW.INI, and add Debug=Yes under the [WAPGW] header. Connect with the phone, and you'll see details in the WAPDEBUG.LOG file ... noted as the Server SDU Size and Client SDU Size. It is also possible that you are using the WAP connection-less protocol instead of the connection-oriented protocol. This protocol does not support segmentation and re-assembly, and Now.WAP imposes a fixed limit of 16KB on responses to connection-less transactions (even if you set the WAPGW.INI file parameter mentioned in this thread). In Nokia terminology, connection-oriented = connection type permanent, connection-less = connection type temporary. So make sure your profile is configured for connection type permanent. And if you really need to transfer data that is larger than the client WAP stack will support, you need to use the "Range:" header (assuming your API into the WAP stack can support this header, and assuming that your content server supports it ... which most of the mainstream web content servers do). Basically, the "Range:" header allows you to request data in chunks, so if you're requesting a large object, you could request the first 50KB, then the next 50KB, etc. -- Kent Williams Now Wireless Support | |||
| Alrick Telfer Unregistered guest |
Hey Kent, talking about files sizes, I was able to download over 10kbs with my phone about 3 weeks ago--in fact I downloaded a game that was 63kbs--but now I get the message, "Page too large to send back." To try and rectify the situation I tried using my cousins sim chip in my phone but it didn't make a difference. I want to know, is the problem my phone, or is it the WAP gateway of my phone company, Cable & Wireless Jamaica? | |||
