Re: [Exist-open] Suppressing HTTP response header (Basic HTTP auth).

[Adam R. <ad...@ex...>]

Hi Chris,

Another option is to authenticate to eXist in a non-protected area by
using your own login form and a xmldb:login in your server script,
then when you access a protected resource you are already
authenticated and not given a 401 response.

On 28 September 2013 00:25, Misztur, Chris <CMi...@ma...> wrote:
> Is it possible to suppress the WWW-AUTHENTICATE http response header on a
> 401 inside the controller.xqy or would this be at the Jetty level?
>
> I have an in-browser restXQ client implementation and I need to eliminate
> the browser's login dialog on a 401.  I am hoping that removing the
> challenge would help.  I am looking at the various web.xml files and I'm not
> quite sure which one is the correct web.xml for the /exist path ?
>
> -c
>
> ________________________________
>
> The contents of this message may be privileged and confidential. Therefore,
> if this message has been received in error, please delete it without reading
> it. Your receipt of this message is not intended to waive any applicable
> privilege. Please do not disseminate this message without the permission of
> the author.
>
> Please consider the environment before printing this e-mail
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>



-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb