You got it. And yes, it does seem that it isn't possible without intervening javascript before going to the cgi code. For doing simple forms, that's not so bad. But when you don't know whether data in a form isn't right until you've gone to the server side (which may require doing db searches, etc.), you're basically forced to redraw the page... and that may also be an equally expensive operation.

Ah, ok, now I kinda get what you want. But what about a simple something like this?

print header;
print <<EOF
<script language="JavaScript">
alert('Hello World');  
history.go(-1);
</script>
EOF
;
[download]

This way, you will get your popup and the user will go straight back to the previous page which probably is still cached (if JavaScript is turned on ... of course). For simple forms, this should be ok.

--
b10m

You got it. And yes, it does seem that it isn't possible without intervening javascript before going to the cgi code. For doing simple forms, that's not so bad. But when you don't know whether data in a form isn't right until you've gone to the server side (which may require doing db searches, etc.), you're basically forced to redraw the page... and that may also be an equally expensive operation.

This is exactly why people use javascript to do client side data validation. It's an extremely common practice to have a bit of javascript triggered before you actually send the datato make sure it's all in the right format. Done correctly theres absolutely no server side work and no communication or time.

But of course you can't trust the client to validate correctly. Never trust the client. You still have to validate server side.