Yes, most definately, thanks for the reinforcement.

Thanks to all who replied, most helpful, keeping to my usual style I normally post what I ended up doing and why:

I've gone with the $ENV{PATH_INFO} idea, because the header stuff caused double prompts and general mess in IE, worked perfectly in Opera though.

However, I'm not actually using the $ENV{PATH_INFO} contents, I'm just calling the CGI in that style and passing the required info via post such as below, 'run' is the CGI and 'cda' is an ExecCGI-d directory:

<form method="POST" action="/cda/run/surtron-020130-03.zip">
<INPUT TYPE="image" src="/images/icon-zip.gif" ALT="Download surtron-0
+20130-03.zip" BORDER="0">
<input type="hidden" name="mode" value="download">
<input type="hidden" name="file" value="surtron-020130-03.zip">
</form>
[download]

This is almost a shortcut I guess, looks neat from the client side and works well in all cases. As long as I check for tainted posts it seems to do what I want.

Update:
I have now changed the above so that the filename hidden field passes a database id instead of the actual filename to make it less h4x0rable.

---

---

• 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.