Please help me to solve the issues in j2me with https

[J.SIVAKUMAR000@GMAIL.COM]

Hi,

Im developing a mobile application in j2me.Im using "Nokia c2-01" mobile for testing.In my application i send a request to one servlet and receive response to mobile via GPRS.I send the request to the servlet through ("https://" ).Here one problem is when i send a request to the server.The request is not hit to server when it goes from mobile application ,but it hits succesfully and get response succefully from server when i type the address ("https://61.......") in the mobile phone's web browser. Here i cannot identify why i cannot able to send the request via my application running in mobile (but it sends succeffully from the mobile phone's browser) My source code snippet is given below

HttpsConnection httpsConnection=(HttpsConnection)Connector.open(url);
InputStream is=httpsConnection.openInputStream();

Here the urs starts from "https://" some url.In my mobile app it throws the "CertificationException".But from mobile phone's web browser it works correctly. Please any one give me ur ideas about this issues.



Additional information: when i use the url "onlinesbi.com";(https://www.onlinesbi.com) (It is a state bank of india's web site) it hits the servlet (server) succeffully from my test mobile phone (nokia c2 01)'s web browser and it also successfully hits from my mobile application also.So i think my phone supports Https.I think there is any changes is needed in the mobile phone's setting.Please help me its an urgent issue



im using test certificate (self signed) in server side.But i does not put the certificate into mobile phone.Here one thing is when i type the url in the web browser of mobile phone it works fine.I think if certificate problem means it is not also work from web browser of mobile phone.Im also tested in "Sony erricson z530i" mobile it works fine.But based on project requirements here my target phone is nokia.If there is any mistake on my comment please forgive me.On past 20 days im not able to solve the issues .So please help me to solve the issues.All ideas are welcome

[skalogir]

Hi,

Does the URL contain characters that need to be URL encoded? If you are passing parameters via URL, the value of these parameters should not contain characters like: ! * ' ( ) ; : @ & = + $ , / ? % # [ ]
If that's the case, these characters need to be encoded.

Browsers can do the encoding automatically, but that's not the case for Java applications.

More information regarding URL encoding here:

http://en.wikipedia.org/wiki/Percent-encoding

Also, have you tried to specify the submission method (either GET or POST) and the content type, just before you open the input stream?

Here is a snippet:

	        httpsConnection.setRequestMethod(HttpsConnection.POST);
	        httpsConnection.setRequestProperty("Content-Type","text/xml");

There is also Nokia's Professional Technical Support Service:
http://www.developer.nokia.com/Resou..._support.xhtml
that can be an option for urgent cases that require immediate solutions.

[im2amit]

I suggest to test the app on Nokia emulator and see if work with HTTPS - URL encoding may be a issue. (try with HTTP)
Other issue your Nokia device may need a signed build of the app to make HTTPS request.

[traud]

your Nokia device may need a signed build of the app to make HTTPS request.

Signing the code is not required for HttpsConnection class(es).

i cannot identify why i cannot able to send the request via my application running in mobile (but it sends succeffully from the mobile phone's browser)

Unfortunately, the internal browser and J2ME use different algorithms and user interactions to handle server certificates. Furthermore in a Nokia C2-01, the browser is actually a proxy based browser which should not be used for HTTPS communication at all – because you do not know who listens at the proxy.

Unfortunately, unfortunately, I do not have an answer to your actual question, just some recommendations…

im using test certificate (self signed) in server side.But i does not put the certificate into mobile phone.

The bottom line from the above recommendations: Create a full blow server, with a correct certificate, from a well-known authority like VeriSign or Entrust. It is near to impossible to do HTTPS in the debugging phase without that. Otherwise you waste more time, than a server-setup is going to cost.
– Instead of using a well-know authority, and creating a self-signed certificates fails because you are not able to install it in your phone.
– Instead of using a domain-name, and utilising IP-addresses as server domain fails because well-known authorities won’t give you a certificate, then.
– Instead of installing the whole chain of certificates, and using only the given certificate fails just like Apple Safari for Mac OS X will fail.
Then, no changes to your phone must be done. Actually, no change to your MIDlet must be done. Not a single code has to be re-written. All you have to do is to change the URL from http:// to https://. Even the class-cast in the line of the Connector.open statement stays the same, because HttpsConnection is a subclass of HttpConnection.