26 aug. 2016 kl. 16:37 skrev Patrick McCormick <duganmccormick@gmail.com>:Thanks, Ken, I added =a host param to TCPSend, but still empty. The target server is =Windows IIS 8 with ASP.net =v4.0.30319. I have to study https://www.w3.org/Protocols/HTTP/1.0/spec.html and =then figure out what parameters my TCPConnect & TCPSend might =be missing.---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list
Most sites like this target =server use a CMS and they all send lots of needless and redundant cruft. = They=E2=80=99re also aggressive about preventing cross domain =hacking, which always seems odd since the point of websites is to =distribute content. I guess they=E2=80=99re trying to prevent Comcast =from accidentally selling something.
TCPConnect & TCPSend should emulate a person at a =browser, but also allow definition of the browser, OS, IP, etc. = I=E2=80=99ve had good luck with this in the distant past. = With modern CMS systems, I think it=E2=80=99s just a matter =of hunting down the parameters necessary to trick the server into =serving a non-human browser.
An organized =list of those requirements covering various combinations of browser, =server & OS would be really handy. Anyone else notice any =glaring omissions in this code:
<!-- HAS_WEBDNA_TAGS -->
[!]=3D=3D=3D=3D=3D Make Connection ==3D=3D=3D=3D=3D[/!]
[text]comcast_result=3D[tcpconnect =host=3Dbusiness.comcast.com&port=3D443&ssl=3DT][!]
[/!][TCPSend skipheader=3DT]GET /ethernet/private-line =HTTP/1.0[UnURL]%0D%0A[/UnURL][!]
[/!]USER-AGENT: =Mozilla/4.0 (compatible; MSIE 5.01; Windows NT =5.0)[UnURL]%0D%0A[/UnURL][!]
[/!]host: business.comcast.com[UnURL]%0D%0A[/UnURL][!]
[/!][/TCPSend][!]
[/!][/tcpconnect][/text]
comcast_result=3D[comcast_result]On Aug 26, 2016, at 6:52 AM, Kenneth Grome =<ken@webdnasolutions.com> wrote:
Try putting a Host parameter inside the tcpsend context. =
It doesn't matter that host is =specified in the tcpconnect tag
because it is =frequently required as a parameter in the tcpsend
context, too. This always works for me:
[text]host=3Dwww.paypal.com[/text]
[text]path=3D/cgi-bin/webscr[/text]
[text]n=3D[unurl]%0D%0A[/unurl][/text]
[text]content=3D... name=3Dvalue pairs go here ...[/text]
[tcpconnect =host=3D[host]&port=3D443&ssl=3DT]
[tcpsend =skipheader=3DT]POST [path] HTTP/1.0[n][!]
[/!]Host: =[host][n][!]
[/!]User-Agent: Mozilla/4.0 (compatible; MSIE =5.01; Windows NT 5.0)[n][!]
[/!]Content-Type: =text/namevalue[n][!]
[/!]Content-Length: =[countchars][content][/countchars][n][n][!]
[/!][content][n][!]
[/!][/tcpsend]
[/tcpconnect]
This has been the =required syntax for years (for most servers).
If =it's not mentioned in the docs it should be.
Regards,
Kenneth Grome
WebDNA =Solutions
http://www.webdnasolutions.com
Web Database =Systems and Linux Server Administration
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To =unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us.To unsubscribe, E-mail to: =div>archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdna.us
|
26 aug. 2016 kl. 16:37 skrev Patrick McCormick <duganmccormick@gmail.com>:Thanks, Ken, I added =a host param to TCPSend, but still empty. The target server is =Windows IIS 8 with ASP.net =v4.0.30319. I have to study https://www.w3.org/Protocols/HTTP/1.0/spec.html and =then figure out what parameters my TCPConnect & TCPSend might =be missing.---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list
Most sites like this target =server use a CMS and they all send lots of needless and redundant cruft. = They=E2=80=99re also aggressive about preventing cross domain =hacking, which always seems odd since the point of websites is to =distribute content. I guess they=E2=80=99re trying to prevent Comcast =from accidentally selling something.
TCPConnect & TCPSend should emulate a person at a =browser, but also allow definition of the browser, OS, IP, etc. = I=E2=80=99ve had good luck with this in the distant past. = With modern CMS systems, I think it=E2=80=99s just a matter =of hunting down the parameters necessary to trick the server into =serving a non-human browser.
An organized =list of those requirements covering various combinations of browser, =server & OS would be really handy. Anyone else notice any =glaring omissions in this code:
<!-- HAS_WEBDNA_TAGS -->
[!]=3D=3D=3D=3D=3D Make Connection ==3D=3D=3D=3D=3D[/!]
[text]comcast_result=3D[tcpconnect =host=3Dbusiness.comcast.com&port=3D443&ssl=3DT][!]
[/!][TCPSend skipheader=3DT]GET /ethernet/private-line =HTTP/1.0[unurl]%0D%0A[/UnURL][!]
[/!]USER-AGENT: =Mozilla/4.0 (compatible; MSIE 5.01; Windows NT =5.0)[unurl]%0D%0A[/UnURL][!]
[/!]host: business.comcast.com[unurl]%0D%0A[/UnURL][!]
[/!][/TCPSend][!]
[/!][/tcpconnect][/text]
comcast_result=3D[comcast_result]On Aug 26, 2016, at 6:52 AM, Kenneth Grome =<ken@webdnasolutions.com> wrote:
Try putting a Host parameter inside the tcpsend context. =
It doesn't matter that host is =specified in the tcpconnect tag
because it is =frequently required as a parameter in the tcpsend
context, too. This always works for me:
[text]host=3Dwww.paypal.com[/text]
[text]path=3D/cgi-bin/webscr[/text]
[text]n=3D[unurl]%0D%0A[/unurl][/text]
[text]content=3D... name=3Dvalue pairs go here ...[/text]
[tcpconnect =host=3D[host]&port=3D443&ssl=3DT]
[tcpsend =skipheader=3DT]POST [path] HTTP/1.0[n][!]
[/!]Host: =[host][n][!]
[/!]User-Agent: Mozilla/4.0 (compatible; MSIE =5.01; Windows NT 5.0)[n][!]
[/!]Content-Type: =text/namevalue[n][!]
[/!]Content-Length: =[countchars][content][/countchars][n][n][!]
[/!][content][n][!]
[/!][/tcpsend]
[/tcpconnect]
This has been the =required syntax for years (for most servers).
If =it's not mentioned in the docs it should be.
Regards,
Kenneth Grome
WebDNA =Solutions
http://www.webdnasolutions.com
Web Database =Systems and Linux Server Administration
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To =unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us.To unsubscribe, E-mail to: =div>archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdna.us
DOWNLOAD WEBDNA NOW!
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...