Re: ASP.Net form not posting!

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Kevin Spencer (kspencer_at_takempis.com)
Date: 11/09/04 

Date: Tue, 9 Nov 2004 16:14:55 -0500

Are you sure that the form is not posting? What makes you think so?

You say that you have "a page with form tags." This sounds suspiciously like
you have a nested form in your page, as an ASP.Net Page is almost always a
WebForm. If you have inserted form tags into a WebForm, you most likely have
a nested form. Nested forms are not a good idea, and generally (depending
upon the browser) misbehave in any number of ways.

A form not posting is not a server-side issue, as the form is an HTML
document that resides on the client machine, in the client browser. Only
once the form has posted (sent a Request to the server) does the server come
into play. Therefore, if the form is not posting, you most likely have a
problem with your client-side HTML (such as nested form tags).

If you post a URL, we can look at the client-side HTML. 

-- 
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Neither a follower
nor a lender be.
<Ian.Suttle@gmail.com> wrote in message
news:1100031713.166964.140510@c13g2000cwb.googlegroups.com...
> I am have been researching this issue to no end, so any help would be
> very much appreciated.
>
> I have a page with form tags.  Inside of the form tags is a panel that
> contains a user control.  The form tags are NOT inside of the user
> control.  Inside that user control are a few panels that contains
> different steps of an application (for applying to something).  When I
> go to step 1 and submit, the asp:validators catch the errors and the
> form doesn't post.  So far this is what I would expect.  Once I correct
> the errors, the validation messages go away, but the form will still
> not post.
>
> Here is what is weird.  This was developed on Windows XP Pro, and works
> flawlessly there.  I have also tested the exact same code on a Windows
> 2000 server and it works perfectly there as well.  As soon as I upload
> this to my production Windows 2003 server it produces the behavior that
> I described above.  I thought to myself that this may be validation
> file issues, but I am using the aspnet_client\system_web\1_1_4322 files
> placed in the root of my application.
>
> This is at a web host, not my own windows 2003 server, so I am somewhat
> limited as to what I can see or do on that server.
>
> Does anyone have ANY ideas at this point?  Any help would be great!
> Thanks,
> Ian Suttle
>
Quantcast