[SOLVED] curl: Port number ended with 'I'

Aquarius_Girl · 10-30-2020, 08:22 AM

From: https://www.ibm.com/support/pages/no...fileoperations

Code:

curl -k -i -X POST -d ' { "path" : "/" }' https://USER:PASSWORD@HOST:9092/files/browse

I tried:

Code:

curl  -k -i -x POST -d '{ "path" : "/" }' https://example.com:abc@@53096wrxgcg.ibmaspera.com:33001/files/workspaces/12345/all/11111:2

Here `example.com` is username, `abc@` is password, `53096wrxgcg.ibmaspera.com` is host.

Error message:

Code:

curl: (3) Port number ended with 'I'

What am I doing wrong here?

berndbausch · 10-30-2020, 08:37 AM

I am not sure what's wrong, but the double @ sign looks incorrect. Also, not -x but -X.

EXIT: The lower-case -x sets the proxy instead of the intended method. I suppose curl gets thoroughly confused by your command string.

Aquarius_Girl · 10-30-2020, 08:38 AM

@ is the part of the password. -x was accidental. I replaced it with -X.

What to do is @ is the part of the password?

dugan · 10-30-2020, 08:48 AM

Can't you just quote the URL?

Aquarius_Girl · 10-30-2020, 08:52 AM

@dugan:

I tried:

Code:

curl  -k -i -X POST -d '{ "path" : "/" }' 'https://example.com':'abc@'@53096wrxgcg.ibmaspera.com:33001/files/workspaces/12345/all/11111:2

It still results in same error.

dugan · 10-30-2020, 08:56 AM

This answer seems to recommend rewriting the command to not use "-X POST".

https://stackoverflow.com/a/58131250/240515

Aquarius_Girl · 10-30-2020, 09:29 AM

This way that error has gone:

Code:

$ curl --local-port 33001 -u abc@pqr.com -k -i -X POST -d '{ "path" : "/" }' http://53096wrxgcg.ibmaspera.com/files/workspaces/12345/all/23456:2

Enter host password for user 'abc@pqr.com':

HTTP/1.1 301 Moved Permanently
Location: https://53096wrxgcg.ibmaspera.com/files/workspaces/12345/all/23456:2
X-Xss-Protection: 1; mode=block
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
X-Content-Security-Policy: default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; img-src 'self' data:; style-src 'self' 'unsafe-inline'
Cache-Control: no-cache
Access-Control-Allow-Credentials: false
Date: Fri, 30 Oct 2020 14:22:14 GMT
Server: ibmaspera.com
Connection: close
Content-Length: 0

pan64 · 10-30-2020, 10:32 AM

didn't you mix the letter i and number 1 ?
from the other hand if username contained a @ you cannot put it into the url, that may cause confusion/conflict. use curl with --user or --netrc (or similar).