It looks like the problem with this site is not with headers, but with some form of protection they now use. The first page that loads (that's given the 503) automatically fills in a form with calculated values (all done in javascript). This form is posted, cookies are set and then the page is loaded again with the real content.
It looks like the problem with this site is not with headers, but with some form of protection they now use. The first page that loads (that's given the 503) automatically fills in a form with calculated values (all done in javascript). This form is posted, cookies are set and then the page is loaded again with the real content.
Thanks, I totally missed that!
Now when logging while requesting the same page in Chrome, I see a totally different "handshake". Will look into it ...
Another question:
- If the cookies are used for authentication, where would the best place to add code for this in the plugin, in the Start routine perhaps?