SSL Soap and Redirects

The redirect is a special HTTP response code that the client can choose to interpret or not. As far as I know, the most common toolkits out there don't support HTTP redirects. But, this is standard in all browsers so your rule should work with HTTP based browser requests.

 

 

As for the load on the device, that is always an issue. If you have the opportunity to modify the url's on the outbound traffic before it hits the device that is the best case. With that being said, the overhead will depend on the payload size and the amount of modifications. Since changing "http" to "https" will require additional memory, you can't get away with a simple memory overwrite, but you'll have to trigger extra re-allocations of the payload to modify the content. For very large payloads this may become an issue for very high levels of traffic. But that should only matter when your device is maxed out connection wise.

 

 

I would apply the rule and do some tests to determine the overhead for your self and then try to get the backend server code to change it's references if you find that the overhead is unacceptable.

 

 

-Joe