HTTPS and Invalid ViewState
Brian Donahue
Posts: 6,590 Bronze 1
Hello,
The invalid viewstate error could be caused by ANTS Load's failure to automatically script HTTP 302 redirections. If you have a line in your script, for example, WebClient.Get("http://localhost"), your next request may generate invalid viewstate because you'd be redirected to http://localhost/default.aspx and ANTS doesn't script that.
If this is happening in your script, you can fix it by adding a line to the script:
I can't think of an excuse for the script recorder not working under SSL, because it does normally work. The script recorder works by launching an instance of Internet Explorer configured to use http://localhost:8000 as a proxy. ANTS Load acts as this proxy and captures all of the HTTP requests before forwarding them on. I'd assume there is a proxy issue there somewhere, such as another proxy on your computer using port 8000.
The invalid viewstate error could be caused by ANTS Load's failure to automatically script HTTP 302 redirections. If you have a line in your script, for example, WebClient.Get("http://localhost"), your next request may generate invalid viewstate because you'd be redirected to http://localhost/default.aspx and ANTS doesn't script that.
If this is happening in your script, you can fix it by adding a line to the script:
That will get the page that you were redirected to and update ANTS Load's viewstate.WebClient.Get("http://localhost")
WebCleint.Get(WebClient.HttpResponse.Location)
I can't think of an excuse for the script recorder not working under SSL, because it does normally work. The script recorder works by launching an instance of Internet Explorer configured to use http://localhost:8000 as a proxy. ANTS Load acts as this proxy and captures all of the HTTP requests before forwarding them on. I'd assume there is a proxy issue there somewhere, such as another proxy on your computer using port 8000.
This discussion has been closed.
Comments