View source

{{KBTS}}
__NOTOC__ 
__NOEDITSECTION__

[[Category:Technical Solution]]

{{KnowledgeBase
|id=TSJ000363
|platform=Series 40 2nd Edition, Series 40 3rd Editions, Series 40 5th Editions, Series 40 6th Edition   
|devices=
|category=Java
|subcategory=
|creationdate=July 7, 2006, updated May 12, 2009
|keywords=
}}

== Overview ==
Using HTTP proxy with Java MIDlets in Nokia Series 40 devices (from 2nd Edition onwards)

== Description ==
As a generic rule, using the HTTP proxy server with Java MIDlets in Nokia Series 40 devices (from 2nd Edition onwards) is not recommended. 
 
However, if there is a need to use the proxy, the operator can send specific settings over the air (OTA) to the device.

Basically, the operator first has to set the proxy in the APN before delivering the APN settings to the device. After the proxy is set, the APN settings can be delivered to the device.

The specific settings are sent via OMA Client Provisioning using the ACCESS characteristic. Please refer to the Forum Nokia document [http://www.forum.nokia.com/info/sw.nokia.com/id/8d85ad81-5a9b-40fe-bf2a-d567dfd755ec/Series_40_DP_2_0_OMA_Client_Provisioning_v1_3_en.pdf.html Series 40 Developer Platform 2.0: OMA Client Provisioning], Section 4.10, Java™ Technology, for more information and details.

Note that this approach has a major drawback — it does not work across configuration contexts, and that effectively restricts the number of configuration contexts to one. For this reason, this option is not recommended at all.

In addition, for certain client applications such as Opera Mini, this issue may be troubleshot by testing both HTTP and Socket-level connections since some networks will block one connection type but not the other. In addition, it is worth trying some different ports at the socket level. The previous points apply to certain client applications only.

[[Category:Java ME]][[Category:Series 40 2nd Edition]][[Category:Connectivity]]