Originally Posted by Dougsg38p
What kind of payload are you sending? You need to align your "content-type" with what the server is expecting. Based on the error, it might be an issue with unnacceptable content type.
>>> The payload is simple textual data and nothing else. The content type is aligned accordingly with what the server can expect.
Many servers will have issues with binary content unlesss you set the content length.
>>> You are right, but if you see the code it is set.
Also, when I asked you about connection parameters, I'm referring to the Blackberry connection parameters. If you are on a device with BES, then you should be appending no parameters to your URL. If you are on a device that is NOT on a BES, you will need some type of connection parameters (like ";deviceside=true" and the APN info). The reason I asked the question is that you may still be appending connection parameters (requesting a Direct TCP connection for insance), and this may be restricted by BES. So, you are almost always going to detect that the device is on BES, and make sure that you are routing though BES, rather than around it.
>>> I will need to implement this and then I can see if this works or not. Would you be able to refer me to a simple application (with source code to analyze) which just communicates with the server to authenticate a user and can successfully run in a BES environment? That would be of great help! Thank you.