Hi,

I dont think it is possible without hacking the browser's sources.

Cezar.
On Mon, 23 Aug 1999, Java List wrote:

> When using HTTP authentication, the webserver asks the client to
> authenticate by sending something like the following in it's HTTP header
>
> WWW-Authenticate Realm="some realm"
>
> The browser then pops up an authentication window and responds with
> something like the following in it's HTTP header:
>
> Authorization: dje9jhge9egh3939e9ff3
>
> The browser then caches this authorization string so that the user doesn't
> get bothered with having to re-authenticate.
>
> I'd like to use a custom login screen (rather than the default HTTP
> login/paswd window) AND still tell the client to send the Authorization
> string in it's Authorization HTTP header.   I'd like to take the user's
> form data and from it generate the Authorization HTTP header to send back
> to the server.  Has anyone done this and have any ideas to share??  The
> Jason Hunter "bible" talks about a few other methods and none of them go
> over using a custom login screen while ALSO using the HTTP authorization
> behind the scenes.   Thanks,
>
> -Nash
>
> ___________________________________________________________________________
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff SERVLET-INTEREST".
>
> Archives: http://archives.java.sun.com/archives/servlet-interest.html
> Resources: http://java.sun.com/products/servlet/external-resources.html
> LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
>

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html

Reply via email to