TF logon problems with ATT

[rgano]

My normal ISP is Mediacom, which am now using. Hurricane Michael knocked Mediacom out for four months and 11 days, and in the interim, I went with an ATT hotspot which would not allow me to log onto this website. I went with this laptop to a relative's home in an unaffected area nad used his Mediacom to log in. With my hotspot there, we tried to log on with his computer - no luck. Back home again with hotspt, still no luck. Got Mediacom back a couple days back, and viola, I can log on to ths website once more. We pinged ATT about it, and they said they would look into it - nothing heard. Since others have said here that they use ATT ok, I can only assume it is a regional issue. Anyway, I'M BACK!

 

[Janet H]

I'm sorry you had trouble. Did they give you any details? Interested...

 

[Shrew]

You already have a post addressing this situation.

http://www.trawlerforum.com/forums/s22/trouble-logging-att-hot-spot-41405-2.html

There were several suggestions that you "Click the 'remember me' box before logging on".

Did you ever get a chance to go through that step?

 

[rgano]

I tried every suggestion given at the time. We left the problem in ATT's lap, and they did nothing.

 

[Shrew]

I would download either Fiddler2 or Fiddler4 and install it on the computer. I would close all browser sessions, then flush browser cache. I would then start a Fiddler trace and then logon to the site.

I could take a look at the Fiddler Trace and analyze the flow. This should be a simple HTML Form Auth. I'd expect to see a flow something like:

=================================
[Initial GET to Trawler Forum from the web browser]

-> REQUEST: GET http://www.trawlerforum.com/forums/ HTTP/1.1

-> RESPONSE: HTTP/1.1 200 OK
(http://www.trawlerforum.com/forums/) is returned to the web browser

------------------------------------------------------------------
[GET resulting from 'clicking' the "Click Here to Login" link (button)]

-> REQUEST: GET https://www.trawlerforum.com/forums/misc.php?do=login HTTP/1.1
Referer: http://www.trawlerforum.com/forums/

-> RESPONSE: HTTP/1.1 200 OK

------------------------------------------------------------------
[Submitting credentials (User Name and Password) and clicking the "Log In" button.]

REQUEST: POST https://www.trawlerforum.com/forums/login.php?do=login HTTP/1.1
Origin: https://www.trawlerforum.com

RESPONSE: HTTP/1.1 200 OK
(POsting credentials is successful

------------------------------------------------------------------
[Server redirecting the web browser back to the protected resource (page) the request originated from.]

-> REQUEST: GET https://www.trawlerforum.com/forums/ HTTP/1.1
Referer: https://www.trawlerforum.com/forums/login.php?do=login

-> RESPONSE: HTTP/1.1 301 Moved Permanently
Location: http://www.trawlerforum.com/forums/

(Web Server response is redirecting web browser from https to http.

------------------------------------------------------------------
[WEb Browser request for the http resource as a result of the server redirect.]

REQUEST: GET http://www.trawlerforum.com/forums/ HTTP/1.1

RESPONSE: HTTP/1.1 200 OK

web page is returned and user is logged in.

------------------------------------------------------------------


simply indicating that it is 'not working' is not enough information. We would need to understand WHERE in the flow it is failing. We would need to determine if the request is not being sent from the browser, or if the browser is not recieving a response from the server. If so, during which step in the transaction??

 

[rgano]

Thanks for the suggestion, but the problem is no longer an issue since my original ISP is now restored, and the ATT hotspot on which the problem was occurring has been shelved.