Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Security / February 2004

Tip: Looking for answers? Try searching our database.

Is it possible to screen scrape a secure site (HTTPS).....

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Ollie - 25 Feb 2004 10:08 GMT
I know you can screen scrape a website using the System.Net.HttpWebResponse
& System.Net.HttpWebRequest classes.

But how do you screen scrape a secured website (https) that takes a username
& password, I guess what I am asking where does the username & password
go and where do you store any returned token for further requests...

Cheers

Ollie
Max - 25 Feb 2004 10:59 GMT
This might work?
https://username:password@www.domain.com

> I know you can screen scrape a website using the System.Net.HttpWebResponse
> & System.Net.HttpWebRequest classes.
[quoted text clipped - 6 lines]
>
> Ollie
Eric Lawrence [MSFT] - 25 Feb 2004 18:42 GMT
There's probably a property on the object to allow you to add your
credentials.

If not, it's still pretty easy.  First, figure out what protocol the secure
site is using for authentication-- is it BASIC, DIGEST, Negotiate, or
whatever.  If it's basic, it's simple-- just add an Authorization header
with the base-64 encoded username:password string.  If it's digest or
Negotiate, it gets trickier.

Signature

Thanks,

Eric Lawrence
Program Manager
Assistance and Worldwide Services

This posting is provided "AS IS" with no warranties, and confers no rights.

> This might work?
> https://username:password@www.domain.com
[quoted text clipped - 11 lines]
> >
> > Ollie
Chad Z. Hower aka Kudzu - 25 Feb 2004 18:51 GMT
"Eric Lawrence [MSFT]" <e_lawrence@hotmail.com> wrote in news:#5pIH88#DHA.808
@TK2MSFTNGP12.phx.gbl:
> If not, it's still pretty easy.  First, figure out what protocol the secure
> site is using for authentication-- is it BASIC, DIGEST, Negotiate, or
> whatever.  If it's basic, it's simple-- just add an Authorization header
> with the base-64 encoded username:password string.  If it's digest or
> Negotiate, it gets trickier.

Indy supports all of these authentications and more. Its also free.

http://www.indyproject.org/

The only problem is that the .net version doesnt support SSL yet. BUT you
could bundle it with an SSL tunnel if your options are limited.

--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
     "Programming is an art form that fights back"

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.