"EnTerr" wrote:
Why can't ifHttpAgent ensure that a (system) default certificate set is used if not overridden by user? I never had to manually add certificate chain in other programming environments.
That, my friend, is a very good question. My framework/utility functions always add the default certificate (with an override as a parameter) for precisely this reason. What's more annoying is that it's not supported on all screen types (I'm looking at you roGridScreen) or components (I'm looking at you roTextureRequest)... requiring you to download the images to tmp: first to work around it.
EDIT: Oops, my mistake. roTextureRequest does support SetCertificatesFile. It doesn't, however, support EnablePeerVerification like roUrlTransfer, which is what has caused me much grief recently. It'd be nice if they moved all of the certificate specific methods to the ifHttpAgent interface, so they could be used anywhere certificates might need to be specified.
My Channels: http://roku.permanence.com - Twitter: @TheEndlessDev
Instant Watch Browser (NetflixIWB), Aquarium Screensaver (AQUARIUM), Clever Clocks Screensaver (CLEVERCLOCKS), iTunes Podcasts (ITPC), My Channels (MYCHANNELS)