Macrobyte Resources Conversant Developer Central
Internet groupware development platform
HTTP Authentication: how can I hard-code it in the URL?




 

Topic: HTTP Authentication: how can I hard-code it in the URL?

Shown in forward chronological order.
Reverse chronological order | Hierarchical outline view

Messages: 2 of 2.
Pages: 1
HTTP Authentication: how can I hard-code it in the URL? (#309)
Posted: 6/14/2002; 12:55 PM by Clark Venable
Modified: 6/16/2002; 5:28 PM by Clark Venable
Response to: Top of Thread.
Edit | Reply
I'm going to be using HTTP authentication in Conversant to limit access to our intranet site at http:// www.pennstateanesthesia.org/.

Seth wrote a tool for me called Downstreamer which can synchronize what's on the web with what's on the user hard disk. It uses a simple http url get a directory.opml file. Is there a way for this continue to work if I start using HTTP authentication? Would I hard code the username and password in to the url (http://user:password@www.pennstateanesthesia.org/intranet/)?

Clark

Re: Untitled (#313)
Posted: 6/14/2002; 1:59 PM by Seth Dillingham
Modified: 6/14/2002; 1:59 PM by Seth Dillingham
Response to: 309
Edit | Reply

On 6/14/02, Clark Venable said:

>I'm going to be using HTTP authentication in Conversant to limit
>access to our intranet site at http://www.pennstateanesthesia.org/.
>
>Seth wrote a tool for me called Downstreamer which can synchronize
>what's on the web with what's on the user hard disk. It uses a simple
>http url get a directory.opml file. Is there a way for this continue
>to work if I start using HTTP authentication? Would I hard code the
>username and password in to the url
>(http://user:password@www.pennstateanesthesia.org/intranet/)?

(What Clark didn't make clear here is that Downstreamer runs in Radio Userland, and has nothing to do with Conversant.)

I think that adding the username and password into the URL would work, but that means that everybody running the downstreamer will have to do that, and then whenever they change their passwords they'll have to remember to change the URL. Not good.

Probably the best solution is to simply add support for HTTP Authentication to the downstreamer.

Seth

Messages: 2.
Pages: 1


 
© 2002 Macrobyte Resources. All rights reserved.