On 1/17/2018 3:03 PM, Garcia, Jerry E wrote:
>
> Ok, I understand that this is the way it is supposed to work and I got
> it to see the correct file to upload.  But I am still having an issue
> with uploading the file to Share Point, getting a:
>
> HTTP/1.1 401 Unauthorized
>
> HTTP/1.1 404 Not Found.
>
>  
>
> I will add the verbose output:
>
>  
>
> Here is the curl command:
>
>  
>
> /usr/local/bin/curl --ntlm --user username:password --upload-file
> /home/lm446abc/temp/bpmaips-ti01/configValidationReport_DPS-TIAIBPM.html
> --cacert /data/certs/certRepo
> https://collab2.web.boeing.com/sites/BPMOps/_layouts/15/Shared%20Documents/Forms/
> -v
>
>  
>
> Here is the ouput from the verbose:
>
>  
>
> *   Trying 137.137.15.139...
>
> * TCP_NODELAY set
>
> * Connected to collab2.web.boeing.com (137.137.15.139) port 443 (#0)
>
> * ALPN, offering http/1.1
>
> * successfully set certificate verify locations:
>
> *   CAfile: /data/certs/certRepo
>
>   CApath: none
>
> * TLSv1.2 (OUT), TLS handshake, Client hello (1):
>
> * TLSv1.2 (IN), TLS handshake, Server hello (2):
>
> * TLSv1.2 (IN), TLS handshake, Certificate (11):
>
> * TLSv1.2 (IN), TLS handshake, Server key exchange (12):
>
> * TLSv1.2 (IN), TLS handshake, Server finished (14):
>
> * TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
>
> * TLSv1.2 (OUT), TLS change cipher, Client hello (1):
>
> * TLSv1.2 (OUT), TLS handshake, Finished (20):
>
> * TLSv1.2 (IN), TLS handshake, Finished (20):
>
> * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-SHA384
>
> * ALPN, server did not agree to a protocol
>
> * Server certificate:
>
> *  subject: C=US; O=Boeing; OU=servers; CN=collab2.web.boeing.com
>
> *  start date: Jun 12 13:22:15 2017 GMT
>
> *  expire date: Aug 11 13:22:15 2019 GMT
>
> *  subjectAltName: host "collab2.web.boeing.com" matched cert's
> "collab2.web.boeing.com"
>
> *  issuer: C=US; O=Boeing; OU=certservers; CN=Boeing Basic Assurance
> Software Issuing CA G3
>
> *  SSL certificate verify ok.
>
> * Server auth using NTLM with user 'lm446a'
>
> > PUT
> /sites/BPMOps/_layouts/15/Shared%20Documents/Forms/configValidationReport_DPS-TIAIBPM.html
> HTTP/1.1
>
> > Host: collab2.web.boeing.com
>
> > Authorization: NTLM TlRMTVNTUAABAAAABoIIAAAAAAAAAAAAAAAAAAAAAAA=
>
> > User-Agent: curl/7.58.0-DEV
>
> > Accept: */*
>
> > Content-Length: 0
>
> >
>
> < HTTP/1.1 401 Unauthorized
>
> < Server: Microsoft-IIS/8.0
>
> < WWW-Authenticate: NTLM
> TlRMTVNTUAACAAAAAgACADgAAAAGgokCfCo8Zh6hYLEAAAAAAAAAALIAsgA6AAAABgLwIwAAAA9OVwIABABOAFcAAQAUAEUAUwBTAC0ARQBXAEEALQAyADQABAAiAG4AdwAuAG4AbwBzAC4AYgBvAGUAaQBuAGcALgBjAG8AbQADADgARQBTAFMALQBFAFcAQQAtADIANAAuAG4AdwAuAG4AbwBzAC4AYgBvAGUAaQBuAGcALgBjAG8AbQAFABwAbgBvAHMALgBiAG8AZQBpAG4AZwAuAGMAbwBtAAcACAArC5LCsI/TAQAAAAA=
>
> < SPRequestGuid: 3c72419e-cc38-303b-cb70-9fc630c719ff
>
> < request-id: 3c72419e-cc38-303b-cb70-9fc630c719ff
>
> < X-FRAME-OPTIONS: SAMEORIGIN
>
> < SPRequestDuration: 2
>
> < SPIisLatency: 1
>
> < WWW-Authenticate: Basic realm="collab2.web.boeing.com"
>
> < X-Powered-By: ASP.NET
>
> < MicrosoftSharePointTeamServices: 15.0.0.4737
>
> < X-Content-Type-Options: nosniff
>
> < X-MS-InvokeApp: 1; RequireReadOnly
>
> < Date: Wed, 17 Jan 2018 16:32:25 GMT
>
> < Content-Length: 0
>
> < Set-Cookie: BIGipServercollab2-ew-80-pool=3424160137.20480.0000; path=/
>
> <
>
> * Connection #0 to host collab2.web.boeing.com left intact
>
> * Issue another request to this URL:
> 'https://collab2.web.boeing.com/sites/BPMOps/_layouts/15/Shared%20Documents/Forms/configValidationReport_DPS-TIAIBPM.html'
>
> * Found bundle for host collab2.web.boeing.com: 0xace530 [can pipeline]
>
> * Re-using existing connection! (#0) with host collab2.web.boeing.com
>
> * Connected to collab2.web.boeing.com (137.137.15.139) port 443 (#0)
>
> * Server auth using NTLM with user 'lm446a'
>
> > PUT
> /sites/BPMOps/_layouts/15/Shared%20Documents/Forms/configValidationReport_DPS-TIAIBPM.html
> HTTP/1.1
>
> > Host: collab2.web.boeing.com
>
> > Authorization: NTLM
> TlRMTVNTUAADAAAAGAAYAEAAAADiAOIAWAAAAAAAAAA6AQAABgAGADoBAAALAAsAQAEAAAAAAAAAAAAABoKJAjWnZEF/rktBUrN9zFb1BDwcv8V7V6zMil0a434QL0U88oG4gJE2INIBAQAAAAAAAAAJQsKwj9MBHL/Fe1eszIoAAAAAAgAEAE4AVwABABQARQBTAFMALQBFAFcAQQAtADIANAAEACIAbgB3AC4AbgBvAHMALgBiAG8AZQBpAG4AZwAuAGMAbwBtAAMAOABFAFMAUwAtAEUAVwBBAC0AMgA0AC4AbgB3AC4AbgBvAHMALgBiAG8AZQBpAG4AZwAuAGMAbwBtAAUAHABuAG8AcwAuAGIAbwBlAGkAbgBnAC4AYwBvAG0ABwAIACsLksKwj9MBAAAAAAAAAABsbTQ0NmFzYmw3MDAwMjUzOA==
>
> > User-Agent: curl/7.58.0-DEV
>
> > Accept: */*
>
> > Content-Length: 25898
>
> > Expect: 100-continue
>
> >
>
> < HTTP/1.1 404 Not Found
>
> < Server: Microsoft-IIS/8.0
>
> < X-SharePointHealthScore: 0
>
> < SPRequestGuid: 3c72419e-bc3b-303b-cb70-922d85503444
>
> < request-id: 3c72419e-bc3b-303b-cb70-922d85503444
>
> < X-FRAME-OPTIONS: SAMEORIGIN
>
> < SPRequestDuration: 23
>
> < SPIisLatency: 0
>
> < Persistent-Auth: true
>
> < X-Powered-By: ASP.NET
>
> < MicrosoftSharePointTeamServices: 15.0.0.4737
>
> < X-Content-Type-Options: nosniff
>
> < X-MS-InvokeApp: 1; RequireReadOnly
>
> < Date: Wed, 17 Jan 2018 16:32:25 GMT
>
> < Content-Length: 0
>
> < Connection: close
>
> <
>
> * Closing connection 0
>
> * TLSv1.2 (OUT), TLS alert, Client hello (1):
>
>  
>
>  
>
> What am I doing wrong????
>

Please don't top-post it makes the conversation hard to follow [1]. The
initial 401 unauthorized is expected, it includes an auth challenge that
curl then fulfills on the subsequent request. Why the server's response
to that request is 404 not found I really don't know, that's something
you'd have to ask them. It's possible PUT is just not allowed.

[1]: https://curl.haxx.se/mail/etiquette.html#Do_Not_Top_Post

-----------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-users
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2018-01-19