I'm discovering that Elaine 2.0 (the new Palm.net proxy currently in testing) doesn't seem too happy with pre-PalmOS 4.0 INetLib programs. Specifically, the default content type is something with lots of odd transformations. Earlier tonight, I was using a 3.5-vintage version of INetLow with a the 4.0 full ROM. This ROM directs INetLib apps to proxy.palm.net, a machine running Elaine 2. I noticed that the string "[da.a]" sent as part of a HTTP POST got transformed into "0.0.0", something my server code didn't like at all. In doing more experiments, I also saw arbitrary characters getting URL-encoded by the proxy before being sent on to my server. When I updated to the 4.0 sample version of INetLow (see other post for the compilation problem I noted), my post got through without problem. The significant line was a new call to INetLibSockSettingSet that sets inetSockSettingContentType to "application/x-www-form-urlencoded". When I commented out that line, I got the bad behavior again. So, I backed down to a 3.5 ROM and tried to run the 4.0 INetLow example on it. No luck, as the inetSockSettingContentType setting isn't implemented. Now, I tried the 3.5 ROM with the 3.5 INetLow, but changed my proxy to the new Elaine. This worked, but duplicated the result with the invalid data getting posted. I would highly urge Palm to change the Elaine 2.0 code to treat untyped POSTs as being of type application/x-url-encoded. The current change breaks old INetLib applications when run against the proxy, even on old devices. I'm not sure what content type is considered default now, but whatever it is, it stinks! -- Ben Combee Veriprise Wireless <http://www.veriprise.com> -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
