Help with slow network messages

Question

Help with slow network messages

Navigation

#1 by (0 votes)

1

I have an extremely strange case, who could help me solve it, I have a website developed in vs2005, there is a front and a back, the back is web service and the front is aspx, the back is connected to the BD, good that as a summary. The extremely rare thing is that in the authenticate I have this code:

bool Authenticated = ServicioWeb.validar(txtUser.Text,txtpass.Text);
if (Authenticated)
    {
        Session["Usuario"] = txtUser.Text;
        Response.Redirect("resCambio.aspx", false);            
    }
    else
    {
        lblError.Text = "usuario no valido."; 
    }

As you can see is quite simple, the strange thing is that if the network from which I use the website is slow it shows the message of the path of false, if the network is 4g or higher the user can authenticate normally, eye that the back as the front are in the same server, but I do not understand why the slow networks are going through the false, the code of the validate method of the back is quite simpel only a select to the user.

asp.net

asked by RSillerico 23.08.2016 в 15:54

source

1 answer

Pass data / variable PHP to modal Bootstrap 3 from SVG path What is the port used by the GPS sensor that comes in a tablet?

score 0 · Accepted Answer

I understand that both the site with the aspx pages and the asmx service are under the same IIS in different website

It is clear that the speed of connection from the client is not the problem since it does not affect how the aspx connects with the aspx when the user validates. Also if you return false means that the service responds.

You could in the code define the log code to a file to see what path the execution takes, it is more possible to log the StopWatch to see the delay in response

If in the code you have error controls with try ... catch quitalos so that if there is a failure that could change the validation logic, it is not generated and you can see the problem on the screen, thus discarding an exception incorrectly controlled generates this problem.