> Based on Gabrieles code a short demo. Hope it makes some sense. > Accessing cookie-pages. > A very raw demo, cookie-parsing needs lots of improvements.
> browser-demo: http://polly.rebol.it/cgi-bin/cookie-demo.cgi > cgi-source: http://polly.rebol.it/test/test/cookie-demo/cookie-demo.cgi > rebol client-demo: http://polly.rebol.it/test/test/cookie-demo/cookie-demo.r Ciao Volker, The last example matches part of the output obtained using HTTP TOOLS. I need only further parsing on the values of the cookie but that's simple now. A last question remains. HTTP TOOLS does the following 1) It issues a "/ POST" command 2) Then he sends the header 3) He put the encoded data using the command: "insert http-port-private encoded-data" Here is the HTTP POST header taken from HTTP TOOLS. HTTP-Post-Header: make object! [ Accept: "text/html" User-Agent: reform ["REBOL" system/version] Host: port-spec/host Content-Type: "application/x-www-form-urlencoded" Content-Length: length? encoded-data Cookie: http-tools-data/cookie-data Authorization: join {Basic } enbase rejoin [http-tools-data/username ":" http-tools-data/password] ] The questions are: DOES open/custom issues a "/ POST" command too ? If the answer is YES: How to express the encoded data after the header ? Giuseppe Chillemi -- To unsubscribe from the list, just send an email to lists at rebol.com with unsubscribe as the subject.
