Stuck on "Session Expired"

I've been building and running scrapes for quite a while now, and I haven't gotten this stuck in a long time. I'm trying to make what seems to be a pretty straightforward POST request from the following URL:

http://www.autozone.com/autozone/storelocator/storeLocatorMain.jsp

I used the area code field, but it doesn't matter which criteria you use. I ran it through the proxy session, then copied the transaction and tried to run it on it's own to make sure I got the same result, but instead, I got the following error:

SESSION EXPIRED
Your login session has expired, please login again.

I figured there was a cookie issue, so I had the session visit a page or two beforehand to make sure the right cookies were set. Still nothing, so I tried different cookie policies, then manually setting cookies (which I think were just analytics cookies, anyway). I used the alpha feature where the it compares the last request to the proxy request, and everything matched (except some of the session id values, but that should be different for different instances of requests). I just can't seem to get anything at all except for this error.

Any help, even just pointing me in the right direction, would be greatly appreciated.

It works now...

Well, I tried rebuilding from scratch one more time, and for some reason, it works now. I think there was some stray cookie in there that was throwing things off. Thanks for you help.

Hmm... I proxied it while

Hmm...

I proxied it while searching on the are code 859, and I made a scrapeableFile out of the very first thing that came through my proxy, and it seems to work alright.

I was almost expecting there to be a javascript redirect on the LastResponse tab, which was eventually causing the timeout message.

Can you try to reproduce this? Again, the only information I gave it was the 859 area code, and without further alteration, it seems to run in a session just fine.

I have seen sites that tell you your session timed out, even when that's completely fictitious. It's like their error handling on their side just defaults to such a message.

I wanted to make one

I wanted to make one clarification as well. The "error" I'm getting is not in Screen-scraper itself, but in the resulting page that is returned by the scrapeable file itself. Were you able to get actual results in the html back?

Well, that's just

Well, that's just frustrating. I've run it exactly this way, and every other which way I can think of. In the meantime, I also tried it with tor/privoxy, and using Internet Explorer as the HTTP client, still nothing.

Would it be possible to send me the scrapeableFile you made that was successful? You can email it to me at chrishathaway AT gmail DOT com.

Thanks.