| Author |
Message |
roy
Joined: 17 Sep 2007
Posts: 3
|
 Posted: Mon Sep 17, 2007 6:24 am Post subject: Cookie Handling?! |
 |
|
If the sites uses cookies to store login information after submitting a login form where you have to provide your username and password.. how does this work with Web Dumper?
The existing authentication option does not work in this case. Logging in via the default web browser first and then using the tool does not work either.
Any Ideas?
Thanks |
|
| Back to top |
|
 |
stanbusk
Site Admin
Joined: 28 Dec 2005
Posts: 2387
|
| Posted: Mon Sep 17, 2007 10:09 am Post subject: |
|
|
| Web Dumper supports basic cookie handling. I say basic because it only get them and resend them on demand. |
|
| Back to top |
|
|
roy
Joined: 17 Sep 2007
Posts: 3
|
| Posted: Mon Sep 17, 2007 10:15 am Post subject: |
|
|
| stanbusk wrote: | | Web Dumper supports basic cookie handling. I say basic because it only get them and resend them on demand. |
How do "set the cookie" without the ability to submit a form? Or how do you tell the tool to use an existing cookie from the default browser, especially a session cookie where no file is created for the cookie?
Thanks |
|
| Back to top |
|
|
stanbusk
Site Admin
Joined: 28 Dec 2005
Posts: 2387
|
| Posted: Mon Sep 17, 2007 11:43 am Post subject: |
|
|
| It is the reason why I said it is basic. Web Dumper is unable to send forms. It only save cookies to a file and resend them later. It is all we can do on an automated system. |
|
| Back to top |
|
|
roy
Joined: 17 Sep 2007
Posts: 3
|
| Posted: Mon Sep 17, 2007 6:29 pm Post subject: |
|
|
| stanbusk wrote: | | It is the reason why I said it is basic. Web Dumper is unable to send forms. It only save cookies to a file and resend them later. It is all we can do on an automated system. |
Then you can consider my question to be a suggestion 
Btw. There are several different ways to approach this. The most basic would be that the user can either refer to a permanent cookie to be used for the site (a cookie that was not created by the tool, but earlier in the web browser) and/or add the option to provide the cookie content in a text box to be used for the HTTP requests.
Another more fancier option is to have the user enable his local machine as a proxy and your tool taking the role of a temporarily proxy for a few screens. The user then takes the necessary authentication steps while you capture the created cookies etc. while the requests are processed through your tool (which acts as a proxy). Then you know what cookies (session and permanent) you need for the real requests and the user can change his proxy settings to what they were before.
I hope that makes sense. Cheers! |
|
| Back to top |
|
|
stanbusk
Site Admin
Joined: 28 Dec 2005
Posts: 2387
|
| Posted: Wed Sep 19, 2007 11:27 am Post subject: |
|
|
| I take note. The best would be a way to set a cookie manually despite it would be for quite advanced users. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
