Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!feeder.erje.net!newsfeed.utanet.at!newscore.univie.ac.at!aconews-feed.univie.ac.at!aconews.univie.ac.at!not-for-mail Newsgroups: comp.lang.java.programmer From: Andreas Leitgeb Subject: Re: tools for programming applets References: <028d2009-98b7-43a3-b02d-83eaa89db79e@glegroupsg2000goo.googlegroups.com> Reply-To: avl@logic.at User-Agent: slrn/pre0.9.9-111 (Linux) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: Date: 26 May 2011 16:37:10 GMT Lines: 27 NNTP-Posting-Host: gamma.logic.tuwien.ac.at X-Trace: 1306427830 tunews.univie.ac.at 60386 128.130.175.3 X-Complaints-To: abuse@tuwien.ac.at Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:4604 horos22 wrote: > I was looking to do some quick java development of applets. Here's my > situation: > 1. I have a static server (ie: that I cannot touch) which serves my > client data (and applets). > 2. a bare-bones client programming setup (vim and java compiler) > What I was hoping to do, therefore, is hijack the applets that are > coming from the server, and replace them with my own, compiled ones, > and hook the browser in such a way that when the applet is asked for, > my applet fires instead (hopefully in debugging mode) using the data > from the server as input. If the static server is *not* using https, you could create some proxy (transparent or not) that would intercept the requests for the applet-code but pass through all the rest. It seemed to me on overreading the thread, that this type of operation was not intended by design, so it's *likely* (but not necessarily) so, that no easier way exists. There *may* even exist ways for an https-site, but I won't delve into that. I might perhaps want to visit the USA some time in future and not get arrested for some DMCA-BS applied to a triviality. It's just, that if some web-developer stumbles over this thread, he should under no circumstances come to believe, that "client side security" with applets was anything else than utter insecurity.