G
Griff
I've inherited an ASP application that currently builds up a URL with a
series of keys and values (http://url?key=value&key=value&key=value).
Having built this up programmatically, it then does a Response.Redirect
command.
The problem I have is that I need to add a new key and value to this, but
the existing URL is so long that it almost breaks the limit for the length
of a URL. So, as soon as I add on my new key-value it breaks.
I wondered about shortening the names, but on inspection it appears that my
predecessor has already gone down that path.
What I therefore want to do is to create a form with hidden text fields and
make the form POST the data.
Within the ASP code, it's fairly trivial to build up this form in the same
way that the URL was built up.
However, I now need to SUBMIT this form from my ASP page (running on IIS).
What would be the equivalent of the Response.Redirect command that will now
submit my form?
Or...is there an even better way to go about this....?
Griff
series of keys and values (http://url?key=value&key=value&key=value).
Having built this up programmatically, it then does a Response.Redirect
command.
The problem I have is that I need to add a new key and value to this, but
the existing URL is so long that it almost breaks the limit for the length
of a URL. So, as soon as I add on my new key-value it breaks.
I wondered about shortening the names, but on inspection it appears that my
predecessor has already gone down that path.
What I therefore want to do is to create a form with hidden text fields and
make the form POST the data.
Within the ASP code, it's fairly trivial to build up this form in the same
way that the URL was built up.
However, I now need to SUBMIT this form from my ASP page (running on IIS).
What would be the equivalent of the Response.Redirect command that will now
submit my form?
Or...is there an even better way to go about this....?
Griff