J
Jordan
I have a situation in which I need to:
1. Programmatically construct an html <form... method=POST> (NO
runat=server)
2. My user clicks to POST that form to a separate Web site.
3. When the <form gets posted to the other Web site, the other Web site
responds by showing a new page to my user - the new page is from the other
Web site. Essentially my user gets transferred to the other Web site at the
time the form gets posted.
I'd like to just construct the HTML for the <form> (to be POSTed to the
other site) as a string that gets injected into the aspx page on my site via
a Literal control. But the problem is that this would create a situation
where I have nested <forms (one is mine with runat=server, and the other is
the one I construct in code-behind and inject into the Literal). AFAIK,
nested forms is disallowed by the HTML specification.
So, how can I accomplish this objective? (I have to make this fly with 1.1).
I thought one workaround would be to just use the WebClient to POST the
<form to the other Web site, but I don't think that would allow the other
site to show my user the new page (from the other web site).
Any ideas?
Thanks!
1. Programmatically construct an html <form... method=POST> (NO
runat=server)
2. My user clicks to POST that form to a separate Web site.
3. When the <form gets posted to the other Web site, the other Web site
responds by showing a new page to my user - the new page is from the other
Web site. Essentially my user gets transferred to the other Web site at the
time the form gets posted.
I'd like to just construct the HTML for the <form> (to be POSTed to the
other site) as a string that gets injected into the aspx page on my site via
a Literal control. But the problem is that this would create a situation
where I have nested <forms (one is mine with runat=server, and the other is
the one I construct in code-behind and inject into the Literal). AFAIK,
nested forms is disallowed by the HTML specification.
So, how can I accomplish this objective? (I have to make this fly with 1.1).
I thought one workaround would be to just use the WebClient to POST the
<form to the other Web site, but I don't think that would allow the other
site to show my user the new page (from the other web site).
Any ideas?
Thanks!