Macrobyte Resources Conversant Developer Central
Internet groupware development platform
Re: Untitled




 
Subject Re: Untitled
Posted 6/14/2002; 12:59 PM by Seth Dillingham
Last Modified 6/14/2002; 12:59 PM by Seth Dillingham
In Response To HTTP Authentication: how can I hard-code it in the URL? (#309)
Label None. Read 1518
<Previous Next> Thread: 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

<Previous Next> Thread: Edit Reply
ENCLOSURES

None.
REPLIES

None.


 
© 2002 Macrobyte Resources. All rights reserved.