Re: Environment Variable Question

It appears that you are confusing the Client side of the HTTP connection with the SERVER-side.

The Server WILL see the env variables (if running as CGI). The client side (Your LWP agent) has access to the page generated - nothing else.

In other words, if you want to see what the server got, you will need the server's cooperation - i.e. a page that the server generates (perhaps for debugging) that displays the variables it received.

"There are only two truly infinite things. The universe and stupidity, and I'm not too sure about the universe"- Albert Einstein

Comment on Re: Environment Variable Question

Replies are listed 'Best First'.
Re^2: Environment Variable Question by thekestrel (Friar) on Jun 01, 2005 at 19:12 UTC
NetWallah, I think you're probably right in my confusing the sides of the connection. I assumed there was variables transmitted like env variables back to client side as it seems odd that the server would generate a link to a page and write variables as just placeholders with no dynamic content otherwise whats the point. Thanks for the input. Regards Paul	[reply]
Re^3: Environment Variable Question by NetWallah (Canon) on Jun 02, 2005 at 02:18 UTC
I'll take a shot at guessing the intent of the web page : The {VALUE} placeholder may be used to trigger the receiving page (CGI App) to insert a pre-defined {VALUE} at a pre-determined place or places in response to the clicked item. Without more page context, I cannot speculate further. "There are only two truly infinite things. The universe and stupidity, and I'm not too sure about the universe"- Albert Einstein	[reply]