I can see a few mistakes, and some things you might want to take into consideration.
;Im just trying to view the source here
/echo -a %temp
change to
/echo -a $iif(%temp,$v1,-)
becuase %temp can be nothing sometimes, however I dont think this would stop the script for good.
sockwrite -n $sockname Host:
http://www.***host***.com $+ $crlf $+ $crlf
sockwrite -n $sockname Connection: Keep-Alive
change to
sockwrite -n $sockname Connection: Keep-Alive
sockwrite -n $sockname Host:
http://www.***host***.com $+ $crlf $+ $crlf
becuase your ment to end with a nul line not have stuff after it, not that this should do anything to stop it either.
actually you dont even need "sockwrite -n $sockname Connection: Keep-Alive" (normally)
If after all that the page dont come up as you expect then its likely this
Set-Cookie: SITESERVER=ID=c48189ec1b36b646554cb46c5fb57378; expires=Monday, 01-Jan-2035 00:00:00 GMT; path=/; domain=.***webpage***.com
Set-Cookie: ASPSESSIONIDQATDBSTC=IDJJACKDGHIKJMIOOJJLPMDE; path=/
where you have
sockwrite -n $sockname Host:
http://www.***host***.com $+ $crlf $+ $crlf
try changing to
sockwrite -n $sockname Cookie: SITESERVER=ID=c48189ec1b36b646554cb46c5fb57378; expires=Monday, 01-Jan-2035 00:00:00 GMT; path=/; domain=.***webpage***.com; ASPSESSIONIDQATDBSTC=IDJJACKDGHIKJMIOOJJLPMDE
sockwrite -n $sockname Host:
http://www.***host***.com $+ $crlf $+ $crlf
If that doesnt work, you have to do a two pass system hitting the first time to get the two Set-Cookie:lines and combine them into one Cookie: line then send that with your second attempt.
See
this for some ideas on that.
