I tried this already...
$httpProvider.interceptors.push(function () {
return {
'responseError': function (rejection) {
var s = rejection.status;
return rejection;
}
};
});
But the
I want to say thank you all for your help and many different ways to solve
my problem. I think the most -maybe all- will work in an ideal world without
hard requirements through legacy client-applications. I don't want to hold
on BASIC as auth-method because I like it so much, I prefer to kick
ution is to prefer.
chris, i thank you very much for your help! :-)
and it's nice to see that i'm not the only angularjs developer here... if you
are interested, we can stay in contact at linkedin, skype or so and exchange
best practices... because they are not easy to find for real big angular
applica
-Ursprüngliche Nachricht-
Von: André Warnier (tomcat) [mailto:a...@ice-sa.com]
Gesendet: Mittwoch, 28. Oktober 2015 20:42
An: users@tomcat.apache.org
Betreff: Re: AW: AW: Suppress or replace WWW-Authorization header
On 28.10.2015 17:42, Torsten Rieger wrote:
> -Ursprüngliche Nachri
ication server level.
-Ursprüngliche Nachricht-
Von: André Warnier (tomcat) [mailto:a...@ice-sa.com]
Gesendet: Mittwoch, 28. Oktober 2015 10:26
An: users@tomcat.apache.org
Betreff: Re: Suppress or replace WWW-Authorization header
Hi.
On 28.10.2015 09:36, Torsten Rieger wrote:
> Hi,
&g
-Ursprüngliche Nachricht-
Von: Christopher Schultz [mailto:ch...@christopherschultz.net]
Gesendet: Mittwoch, 28. Oktober 2015 15:39
An: Tomcat Users List <users@tomcat.apache.org>
Betreff: Re: AW: Suppress or replace WWW-Authorization header
Torsten,
On 10/28/15 8:19 AM, Torsten
Hi,
I try to suppress the browser login-dialog on basic authentication (basic
is a legacy requirement), how can I do that? Filters are called after login
on the container, right?
Regards,
Torsten
L FORM
This one looks like this in web.xml :
FORM
webapp global realm
/login.jsp
/error_login.jsp
2015-10-28 16:28 GMT+01:00 Torsten Rieger <torsten.rie...@promatis.de>:
> -Ursprüngliche Nachricht-
> Von: Christopher Schultz [mailto:ch...@chri
Hi,
we are developing a tool with a central repository-server, communication is
implementes based on apache-cxf.
We use a legacy SOAP-based webservice with HTTP-transport and it worked
fine with basic auth.
Since we extended our server-side application with a rest-webservice we
want to change
