There are two options:
- Stick a CGI in between (as you described) and use <base href="$FOO"> or replace any relative URLs in the response from the remote server with absolute URLs. Your client-side problem remains: the URL shown will be that of the CGI in between.
- Do the "form fixing" on the client-side and submit directly to the remote server. You now have a client-side scripting problem.
You can in theory redirect a POST request but IIRC most browsers will do a GET on the new resource. Also, were it to work, you'd still be at square one: you'd be submitting the same data you were submitting before, which was not suitable for consumption by the remote CGI (which is where it's now being sent).
— Arien
-
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.
|