comment on

How about a non perl solution?

A lot of mail clients will do the right thing if a URL is enclosed in < >.

Meaning you email the URL as:
<http://www.server.com/cgi-bin/script/script.plParam1=Value&Param2=value&Param3=value>

If you still need to cut down the length of the URL, I would still look at just passing a session key with the URL and then doing a database lookup based on the key.

Also, rather than building the key lookup into the main cgi script, I suggest that you write a generic redirect script that does the look up.

Meaning, you send <http://www.server.com/cgi-bin/redir.pl?KKDIS47> and the script does a database look on KKDIS47 and then redirects to http://www.server.com/cgi-bin/script/script.plParam1=Value&Param2=value&Param3=value

In reply to Re: Encoding/compress CGI GET parameters by em
in thread Encoding/compress CGI GET parameters by snellm

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.


go ahead... be a heretic
	PerlMonks