Well, my first choice would be for Java to do the work of saving the results on the server before jumping. It's nothing to do with what language each component is, it's just that it seems to me to be the best "responsible party." Encode a similar call to fetch a certain page but don't actually show the results (or the URL) to the user. Then you can jump to a new vanilla URL which shows the results.

Barring that, learn how Java can POST the solved url information rather than GET the solved url information. The POST method hides the values they're sending, while the GET method encodes them into the URL where anyone can see or muck. I'm guessing Java has a way to do that, too. Methods GET and POST in HTML forms - what's the difference?

Barring that, you should encode the URL parameters in such a way that the user can't recognize or muck them. That might mean that your Java and your perl need to share a key.

If you're really trying to avoid all chance of snooping, you'd use a public key encryption scheme, whereby the Java applet only knows a public key and the perl script can read the encoded form in private key. Of course, since Java is a bytecode, easily decompiled language...

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.