Thanks for the reply.
> [...] kind of proxy is this? [...] http/https proxies are expected to work.
Humm ... I hope network team will not see my post so I quote :
- Some two headers in 401 response is "WWW-Authenticate: BASIC realm="Unspecified"" and "Server: BigIP"
- Detail : the main product of this company, same name as the key of keyboard used in a browser for reload the page ^^
=> Standard
> Can you confirm you get auth popup with recent m2e 1.6 build?
No :-(. No authentication popup with v1.6.0.20150203-1921.
In my "home" use case : internet -> reverse-proxy -> maven repository (settings.xml contains only "server" configuration)
In my today "job" use case for test : intranet -> proxy (iron port) -> [internet] -> reverse-proxy -> maven repository (settings.xml contains only "server" & "proxy" configuration)
In this case I have the error message : "Failed to authenticate with proxy"
The wireshark analysis shows :
2) Proxy answer :
---
HTTP/1.1 407 Proxy Authentication Required
Proxy-Authenticate: Basic realm="[The name of] Security Appliance"
...
---
... and nothing else.
=> m2e is supposed to open an authentication popup even if user/password is defined in settings.xml ?
If yes ... perhaps this is the root cause : There is no (logically) preemptive authentication (=> basic auth not in first call) ... but 401/407 doesn't provide popup.
> [...] Can you confirm your configuration uses protocol https?
Yes, I check the bug link : active=true / protocol=https
> [...] need to run m2e through debugger [...]
Humm ... ok. I will try to load m2e source and write unit test in my real case.
Thanks.
Best regards.