Re: Maven and pre-emptive authentication

2015-04-02 Thread Bernd Eckenfels
Hello, the documentation page states that since 3.0.4 it does preemtive auth only for PUT not GET. However it says default preemeptive .. so this sounds like it can still be set? Gruss Bernd Am Tue, 31 Mar 2015 08:57:46 +0100 schrieb James Green james.mk.gr...@gmail.com: So how does one

Re: Maven and pre-emptive authentication

2015-03-31 Thread James Green
So how does one update the documentation to state that pre-emptive authentication is not possible..? On 30 March 2015 at 13:31, Gordon Cody gordon.c...@zafin.com wrote: Hello James It really does try twice. The first time it tries with no credentials supplied. This came to our attention

Re: Maven and pre-emptive authentication

2015-03-31 Thread Arnaud Héritier
Is it related to comments in https://jira.codehaus.org/browse/WAGON-405 ??? For sure the documentation can be updated if required On Tue, Mar 31, 2015 at 9:57 AM, James Green james.mk.gr...@gmail.com wrote: So how does one update the documentation to state that pre-emptive authentication is

Re: Maven and pre-emptive authentication

2015-03-31 Thread James Green
Well spotted. It looks like a tight corner for this functionality what with Central having anonymous GET get authenticated PUT. I guess the behaviour feels unfinished therefore no-one knows what it should be documented as. Irrespective, there seems no obvious way to update these pages as

Maven and pre-emptive authentication

2015-03-30 Thread James Green
I am a little confused. According to: https://maven.apache.org/guides/mini/guide-http-settings.html Maven 3.0.4 defaults to pre-emptive authentication for HTTP PUTs. According to my haproxy logs, each PUT is done twice: 1. PUT happens, receives a 401 response from Nexus 2. PUT happens,

Re: Maven and pre-emptive authentication

2015-03-30 Thread Gordon Cody
Hello James It really does try twice. The first time it tries with no credentials supplied. This came to our attention when we upgraded from maven-2.0.9 to maven-3.0.5. We found out at that time that it had to do with being compliant to some web specification and there was no way to force it to