Details
-
Bug
-
Resolution: Fixed
-
Minor
-
2.9
-
None
-
Sprint 25
Description
The staging ant tasks 1.6.1 use two http client implementations for historical reasons.
The one based on our main client is our Jersey based client which uses preemptive auth by default.
The other one, which does not do pre-emptive auth, is based on a small utility called "Zapper".
The Zapper based client is not doing pre-emptive auth.
Zapper:
PUT /nexus/service/local/staging/deployByRepositoryId/stage-1016/org/sonatype/nexus/example/zen-5664/1.0.0/zen-5664-1.0.0.pom HTTP/1.1 X-Zapper-Transfer-ID ab839b01-cf77-4c68-99b0-d084183570af X-Zapper-Track-ID T2 Content-Length 4769 Host localhost:8081 User-Agent Zapper/1.0-HC4 Regular nexus jersey based client sends pre-auth
Jersey:
POST /nexus/service/local/staging/profiles/137b534d1a150f0c/start HTTP/1.1 Content-Type application/xml; charset=UTF-8 Accept application/xml; charset=UTF-8 Content-Length 107 Host localhost:8081 User-Agent Nexus-Client/2.7.0-02 Cookie JSESSIONID=3a0bf084-1da1-40b6-a3f5-2dfd26c8bfff Cookie2 $Version=1 Authorization Basic YWRtaW46YWRtaW4xMjM=
Attachments
Issue Links
- depends on
-
NEXUS-6841 Improvements to spice-zapper
-
- Closed
-