Looks like Apache config? It's a good idea to specify things like that. The tags confirm it though.
That config only runs when they connect on port 443, so it can't redirect from HTTP.
You can't do a 30 redirect in response to a POST request and keep the arguments unless you convert the request to a GET and write the arguments into the URL. Not really recommended.
You can proxy the request, but I'm not sure that solves your problem.
If the user has already submitted data via POST over an unencrypted connection, and you care about the encryption, you're probably best to let that request break anyway, so it gets noticed and fixed. You should be fixing your form target, and also making sure that the form itself (or the page with AJAX in it or whatever) is sent to the user over HTTPS.
Given that shawsy has said that the problem is that The browser cannot make HTTPS connections to the server, a redirect is definitely not what's wanted. Rather you want to proxy the request:
ProxyPass /GladQE/link https://glad-test.com/GladQE/link.do
ProxyPass /GladQE/retrieve https://glad-test.com/GladQE/retrieve.do
You could alternatively do it with mod_rewrite and RewriteRule.
There are some extra issues to work out if you're changing the domain name, but I think that's not the case here.
Just as an aside, I personally don't like putting host names or IP addresses anywhere except in the server's /etc/hosts file. If you use names in the hosts file like 'web' and 'mysql', which locate services rather than machines, and you refer to those in your apache and other files, then you can move configuration between machines much more easily, knowing that you only have to go over what's in the hosts file.