Absolutely strange inconsistent behavior occuring when a user clicks an ASP.NET button.

[Mossman]

Hello,

I will discuss at a high level what is happening on an ASP.NET web page
I developed a year ago in ASP.NET using Visual Studio 2003 and
currently support.

I have an ASP.NET web page that is broken out into two sections. One
section is where a user enters the main infomation around a financial
outlook record and the second section is dynamic content that generates
a table of values based on the infromation entered in the first section
when the user clicks the ASP.Button. Before the information is
submitted back to the form, I fire a client-side javascript event to
validate the form and prompt the user if they want to save the
information.

Here is the HTML tag of my ASP.Net button.

<asp:button id="btnSave" EnableViewState="False" Runat="server"
CssClass="clsBtnSmall" Text="Save" CausesValidation="False"
OnCommand="CommandBtn_Click" CommandName="Save">

After the client-side validation is successful and the user clicks OK
to save the information, it goes through the code in the Page_Init and
Page_Load before executing to the CommandBtn_Click event.

Now, we have no issues saving the information when we are testing or
any user is testing this form at U.S. sites. It is performing a
Postback to the server when the button is clicked.

However, we have an issue with users down at a site in Mexico. Looking
at the trace logs it is performing a GET operation and not a postback
like when a user clicks a hyperlink on a web page. The strange thing
is this used to work for them.

The only thing I can think of is that this is a network related issue
but I have no way of proving this other than there was a network
separation happening within our organization over a weekend.

Prior to the network separation, this worked for the user in Mexico.

Afterwards, there is an error.

I am not looking at a solution (although I will accept one ). I
looking at "What should I look at first?" scenario.

Any input would be appreciated.

Thanks.

 

[cbDevelopment]

My only guess could be they changed the server config to be cookieless?
When I change mine to cookieless and test a postback, the IIS logs show
my POSTS return a 302, which then trigger a GET.

Hope that helps.

--