I don't know if I would put myself into a position that *depends* on RunRevs implementation of proxy authentication. Even RunRev themselves can't even get it working for their licensing system, so we have off-line activation. It has been this way since Revolution 1.1, (as long as I have been using the product). I do wish it were better.
Have you tried passing proxy authentication in the URL like http://username:passw...@someserver.com/mypage.html? You could save an encrypted preference to populate it behind the scenes, or just store the username, and always prompt for the proxy password. ~Roger On Tue, Aug 20, 2013 at 1:22 PM, Devin Asay <devin_a...@byu.edu> wrote: > Hi all, > > I am a neophyte when it comes to proxy servers. My application phones home > on occasion via HTTP requests (mostly GET but some PUT) to get content > update updates and such. One user has reported that this fails because the > application isn't set up to use his university's proxy server. > > I found the HTTPProxy property in the dictionary. Is it sufficient to give > users a way in my application to enter their HTTP proxy server address? > This is also a point of confusion to me. I thought that the HTTP proxy was > an OS setting that users set up when setting their network settings. Can > anyone point me in the right direction? > > Many thanks. > > Devin > > > Devin Asay > Learn to code with LiveCode University > http://university.livecode.com > > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
