Microsoft MVP성태의 닷넷 이야기
오류 유형: 444. curl로 호출할 때 발생하는 오류 정리 [링크 복사], [링크+제목 복사]
조회: 5193
글쓴 사람
홈페이지
첨부 파일
 

curl로 호출할 때 발생하는 오류 정리

Azure Cognitive 서비스를 curl로 호출할 때 다음과 같이 오류가 발생하는 경우가 있습니다.

C:\> curl -g -v POST "https://eastasia.api.cognitive.microsoft.com/vision/v1.0/analyze?visualFeatures=Categories" -H "Content-Type: application/json" -H "Ocp-Apim-Subscription-Key: ffcd240d42fa4fe98bf0286120fb2801" --data-ascii '{"url": "http://sysnet.blob.core.windows.net/sysnetimages/trip_to_jp_4.png"}'
* Rebuilt URL to: POST/
* Could not resolve host: POST
* Closing connection 0
curl: (6) Could not resolve host: POST
*   Trying 13.94.26.39...
* Connected to eastasia.api.cognitive.microsoft.com (13.94.26.39) port 443 (#1)
* schannel: SSL/TLS connection with eastasia.api.cognitive.microsoft.com port 443 (step 1/3)
* schannel: checking server certificate revocation
* schannel: ALPN, offering http/1.1
* schannel: sending initial handshake data: sending 216 bytes...
* schannel: sent initial handshake data: sent 216 bytes
* schannel: SSL/TLS connection with eastasia.api.cognitive.microsoft.com port 443 (step 2/3)
* schannel: failed to receive handshake, need more data
* schannel: SSL/TLS connection with eastasia.api.cognitive.microsoft.com port 443 (step 2/3)
* schannel: encrypted data buffer: offset 3742 length 4096
* schannel: sending next handshake data: sending 214 bytes...
* schannel: SSL/TLS connection with eastasia.api.cognitive.microsoft.com port 443 (step 2/3)
* schannel: encrypted data buffer: offset 607 length 4096
* schannel: SSL/TLS handshake complete
* schannel: SSL/TLS connection with eastasia.api.cognitive.microsoft.com port 443 (step 3/3)
* ALPN, server did not agree to a protocol
* schannel: incremented credential handle refcount = 1
* schannel: stored credential handle in session cache
> POST /vision/v1.0/analyze?visualFeatures=Categories HTTP/1.1
> Host: eastasia.api.cognitive.microsoft.com
> User-Agent: curl/7.49.0
> Accept: */*
> Content-Type: application/json
> Ocp-Apim-Subscription-Key: ffcd240d42fa4fe98bf0286120fb2801
> Content-Length: 6
>
* upload completely sent off: 6 out of 6 bytes
* schannel: client wants to read 16384 bytes
* schannel: encdata_buffer resized 17408
* schannel: encrypted data buffer: offset 0 length 17408
* schannel: encrypted data got 661
* schannel: encrypted data buffer: offset 661 length 17408
* schannel: decrypted data length: 577
* schannel: decrypted data added: 577
* schannel: decrypted data cached: offset 577 length 16384
* schannel: encrypted data buffer: offset 0 length 17408
* schannel: decrypted data buffer: offset 577 length 16384
* schannel: schannel_recv cleanup
* schannel: decrypted data returned 577
* schannel: decrypted data buffer: offset 0 length 16384
< HTTP/1.1 401 Access Denied
< Content-Length: 143
< Content-Type: application/json
< apim-request-id: b2c7db2c-ef12-48fa-a368-307f127be600
< Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
< x-content-type-options: nosniff
< WWW-Authenticate: AzureApiManagementKey realm="https://eastasia.api.cognitive.microsoft.com/vision/v1.0",name="Ocp-Apim-Subscription-Key",type="header"
< Date: Fri, 05 Jan 2018 01:05:18 GMT
<
{ "statusCode": 401, "message": "Access denied due to invalid subscription key. Make sure to provide a valid key for an active subscription." }* Connection #1 to host eastasia.api.cognitive.microsoft.com left intact
*   Trying 40.83.104.208...
* Connected to sysnet.blob.core.windows.net (40.83.104.208) port 80 (#2)
> POST /sysnetimages/trip_to_jp_4.png}' HTTP/1.1
> Host: sysnet.blob.core.windows.net
> User-Agent: curl/7.49.0
> Accept: */*
> Content-Type: application/json
> Ocp-Apim-Subscription-Key: ffcd240d42fa4fe98bf0286120fb2801
> Content-Length: 6
>
* upload completely sent off: 6 out of 6 bytes
< HTTP/1.1 405 The resource doesn't support specified Http Verb.
< Allow: GET,HEAD,PUT,DELETE
< Content-Length: 237
< Content-Type: application/xml
< Server: Microsoft-HTTPAPI/2.0
< x-ms-request-id: 3bee6302-001e-0034-54c1-85891a000000
< Date: Fri, 05 Jan 2018 01:05:20 GMT
<
?xml version="1.0" encoding="utf-8"?><Error><Code>UnsupportedHttpVerb</Code><Message>The resource doesn't support specified Http Verb.
RequestId:3bee6302-001e-0034-54c1-85891a000000
Time:2018-01-05T01:05:21.1833651Z</Message></Error>* Connection #2 to host sysnet.blob.core.windows.net left intact

"Access denied due to invalid subscription key. Make sure to provide a valid key for an active subscription."라는 오류 메시지는, 물론 잘못된 구독 키를 설정했을 때에도 발생하지만 Azure Cognitive 서비스를 신청한 Region이 다른 경우에도 발생합니다.

즉, "https://westus.api.cognitive.microsoft.com" 지역으로부터 받는 구독 키를 (무심코 예제를 따라 하면서) "https://eastasia.api.cognitive.microsoft.com" 지역으로 HTTP 요청을 날리면 저렇게 접근 오류가 발생합니다.




또 한가지 사례로, curl에 JSON 텍스트를 BODY로 설정할 때 다음과 같은 오류가 발생할 수 있습니다.

C:\> curl -g -v POST "https://westus.api.cognitive.microsoft.com/vision/v1.0/analyze?visualFeatures=Categories" -H "Content-Type: application/json" -H "Ocp-Apim-Subscription-Key: ffcd240d42fa4fe98bf0286120fb2801" -d '{"url": "http://sysnet.blob.core.windows.net/sysnetimages/trip_to_jp_4.png"}'
* Rebuilt URL to: POST/
* Could not resolve host: POST
* Closing connection 0
curl: (6) Could not resolve host: POST
*   Trying 40.112.254.71...
* Connected to westus.api.cognitive.microsoft.com (40.112.254.71) port 443 (#1)
* schannel: SSL/TLS connection with westus.api.cognitive.microsoft.com port 443 (step 1/3)
* schannel: checking server certificate revocation
* schannel: ALPN, offering http/1.1
* schannel: sending initial handshake data: sending 214 bytes...
* schannel: sent initial handshake data: sent 214 bytes
* schannel: SSL/TLS connection with westus.api.cognitive.microsoft.com port 443 (step 2/3)
* schannel: failed to receive handshake, need more data
* schannel: SSL/TLS connection with westus.api.cognitive.microsoft.com port 443 (step 2/3)
* schannel: encrypted data buffer: offset 3742 length 4096
* schannel: sending next handshake data: sending 214 bytes...
* schannel: SSL/TLS connection with westus.api.cognitive.microsoft.com port 443 (step 2/3)
* schannel: encrypted data buffer: offset 607 length 4096
* schannel: SSL/TLS handshake complete
* schannel: SSL/TLS connection with westus.api.cognitive.microsoft.com port 443 (step 3/3)
* ALPN, server did not agree to a protocol
* schannel: incremented credential handle refcount = 1
* schannel: stored credential handle in session cache
> POST /vision/v1.0/analyze?visualFeatures=Categories HTTP/1.1
> Host: westus.api.cognitive.microsoft.com
> User-Agent: curl/7.49.0
> Accept: */*
> Content-Type: application/json
> Ocp-Apim-Subscription-Key: ffcd240d42fa4fe98bf0286120fb2801
> Content-Length: 6
>
* upload completely sent off: 6 out of 6 bytes
* schannel: client wants to read 16384 bytes
* schannel: encdata_buffer resized 17408
* schannel: encrypted data buffer: offset 0 length 17408
* schannel: encrypted data got 581
* schannel: encrypted data buffer: offset 581 length 17408
* schannel: decrypted data length: 506
* schannel: decrypted data added: 506
* schannel: decrypted data cached: offset 506 length 16384
* schannel: encrypted data buffer: offset 0 length 17408
* schannel: decrypted data buffer: offset 506 length 16384
* schannel: schannel_recv cleanup
* schannel: decrypted data returned 506
* schannel: decrypted data buffer: offset 0 length 16384
< HTTP/1.1 400 Bad Request
< Cache-Control: no-cache
< Pragma: no-cache
< Content-Length: 104
< Content-Type: application/json; charset=utf-8
< Expires: -1
< X-AspNet-Version: 4.0.30319
< X-Powered-By: ASP.NET
< apim-request-id: 813bfccc-a48a-485f-9038-a9d03a20a324
< Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
< x-content-type-options: nosniff
< Date: Fri, 05 Jan 2018 01:16:08 GMT
<
{"code":"BadArgument","requestId":"813bfccc-a48a-485f-9038-a9d03a20a324","message":"JSON format error."}* Connection #1 to host westus.api.cognitive.microsoft.com left intact
*   Trying 40.83.104.208...
* Connected to sysnet.blob.core.windows.net (40.83.104.208) port 80 (#2)
> POST /sysnetimages/trip_to_jp_4.png}' HTTP/1.1
> Host: sysnet.blob.core.windows.net
> User-Agent: curl/7.49.0
> Accept: */*
> Content-Type: application/json
> Ocp-Apim-Subscription-Key: ffcd240d42fa4fe98bf0286120fb2801
> Content-Length: 6
>
* upload completely sent off: 6 out of 6 bytes
< HTTP/1.1 405 The resource doesn't support specified Http Verb.
< Allow: GET,HEAD,PUT,DELETE
< Content-Length: 237
< Content-Type: application/xml
< Server: Microsoft-HTTPAPI/2.0
< x-ms-request-id: be36b13a-001e-001a-15c2-8509dd000000
< Date: Fri, 05 Jan 2018 01:16:08 GMT
<
?xml version="1.0" encoding="utf-8"?><Error><Code>UnsupportedHttpVerb</Code><Message>The resource doesn't support specified Http Verb.
RequestId:be36b13a-001e-001a-15c2-8509dd000000
Time:2018-01-05T01:16:08.8793068Z</Message></Error>* Connection #2 to host sysnet.blob.core.windows.net left intact

보는 바와 같이 Request 시의 Content-Length 값이 엉뚱하게 6으로 설정되어 있고, 당연히 "JSON format error."로 "BadArgument" 상황이 발생할 수밖에 없습니다. 검색해 보면,

How to POST JSON data with Curl from Terminal/Commandline to Test Spring REST?
; https://stackoverflow.com/questions/7172784/how-to-post-json-data-with-curl-from-terminal-commandline-to-test-spring-rest

curl의 JSON 텍스트를 명시할 때 작은따옴표를 이용해서는 안 되고 다음과 같이 큰따옴표를 사용하되, 내부의 인용 부호는 esacpe 처리해야 올바로 전달이 됩니다.

curl -g -v POST ...[생략]... -d "{\"url\": \"http://sysnet.blob.core.windows.net/sysnetimages/trip_to_jp_4.png\"}"

또는, escape 처리 대신 내부의 큰따옴표를 작은따옴표로 처리하면 됩니다.

curl -g -v POST ...[생략]... -d "{'url': 'http://sysnet.blob.core.windows.net/sysnetimages/trip_to_jp_4.png'}"

심지어 "How to POST JSON data with Curl from Terminal/Commandline to Test Spring REST?" 글의 덧글에서도 나오지만 많은 인터넷 자료에서 curl의 json 포맷 입력 시 작은따옴표를 묶어서 예시하는 경우가 종종 있는데 그렇게 하면 (아마도 윈도우에서) 정상적인 처리가 안 됩니다.



[2018-10-19 추가] 테스트 인증서를 사용한 https 호출을 하는 경우, "curl: (35) schannel: next InitializeSecurityContext failed: SEC_E_UNTRUSTED_ROOT (0x80090325) - The certificate chain was issued by an authority that is not trusted." 오류가 발생한다면 "-k" 옵션을 설정.




[이 글에 대해서 여러분들과 의견을 공유하고 싶습니다. 틀리거나 미흡한 부분 또는 의문 사항이 있으시면 언제든 댓글 남겨주십시오.]





[최초 등록일: ]
[최종 수정일: 10/19/2018 ]

Creative Commons License
이 저작물은 크리에이티브 커먼즈 코리아 저작자표시-비영리-변경금지 2.0 대한민국 라이센스에 따라 이용하실 수 있습니다.
by SeongTae Jeong, mailto:techsharer@outlook.com

비밀번호

댓글 쓴 사람
 




... 16  17  18  19  20  21  22  23  24  25  26  27  28  [29]  30  ...
NoWriterDateCnt.TitleFile(s)
11506정성태6/27/20185708.NET Framework: 740. C#에서 enum을 boxing 없이 int로 변환하기 - 두 번째 이야기 [7]파일 다운로드1
11505정성태4/19/20182384개발 환경 구성: 371. Azure Web App 확장 예제 - Simple WebSite Extension
11504정성태4/19/20182538오류 유형: 465. Azure Web App 확장 - Extplorer File manager 적용 시 오류
11503정성태4/19/20182499오류 유형: 464. PowerShell - Start-Service 명령 오류 (Service 'xxx' cannot be started)
11502정성태5/12/20183443개발 환경 구성: 370. Azure VM/App Services(Web Apps)에 Let's Encrypt 무료 인증서 적용 방법 [2]
11501정성태4/17/20182316개발 환경 구성: 369. New-AzureRmADServicePrincipal로 생성한 계정의 clientSecret, key 값을 구하는 방법파일 다운로드1
11500정성태4/17/20182622개발 환경 구성: 368. PowerShell로 접근하는 Azure의 Access control 보안과 Azure Active Directory의 계정 관리 서비스
11499정성태4/17/20182202개발 환경 구성: 367. Azure - New-AzureRmADServicePrincipal / New-AzureRmRoleAssignment 명령어
11498정성태4/17/20182201개발 환경 구성: 366. Actvie Azure Directory의 사용자 유형 구분 - Guest/Member
11497정성태4/17/20182373개발 환경 구성: 365. Azure 리소스의 액세스 제어(Access control) 별로 사용자에게 권한을 할당하는 방법 [2]
11496정성태4/17/20181954개발 환경 구성: 364. Azure Portal에서 구독(Subscriptions) 메뉴가 보이지 않는 경우
11495정성태4/18/20182548개발 환경 구성: 363. Azure의 Access control 보안과 Azure Active Directory의 계정 관리 서비스
11494정성태4/16/20182326개발 환경 구성: 362. Azure Web Apps(App Services)에 사용자 DNS를 지정하는 방법
11493정성태4/16/20182325개발 환경 구성: 361. Azure Web App(App Service)의 HTTP/2 프로토콜 지원
11492정성태4/13/20182275개발 환경 구성: 360. Azure Active Directory의 사용자 도메인 지정 방법
11491정성태9/30/20192552개발 환경 구성: 359. Azure 가상 머신에 Web Application을 배포하는 방법
11490정성태4/12/20183207.NET Framework: 739. .NET Framework 4.7.1의 새 기능 - Configuration builders [1]파일 다운로드1
11489정성태4/12/20182409오류 유형: 463. 윈도우 백업 오류 - a Volume Shadow Copy Service operation failed.
11488정성태4/12/20182276오류 유형: 462. Unhandled Exception in Managed Code Snap-in - FX:{811FD892-5EB4-4E73-A147-F1E079E36C4E}
11487정성태4/12/20182460디버깅 기술: 115. windbg - 닷넷 메모리 덤프에서 정적(static) 필드 값을 조사하는 방법
11486정성태4/11/20182499오류 유형: 461. Error MSB4064 The "ComputeOutputOnly" parameter is not supported by the "VsTsc" task
11485정성태4/11/20184553.NET Framework: 738. C# - Console 프로그램이 Ctrl+C 종료 시점을 감지하는 방법파일 다운로드1
11484정성태4/11/20183557.NET Framework: 737. C# - async를 Task 타입이 아닌 사용자 정의 타입에 적용하는 방법파일 다운로드1
11483정성태4/10/20186039개발 환경 구성: 358. "Let's Encrypt"에서 제공하는 무료 SSL 인증서를 IIS에 적용하는 방법 (2) [1]
11482정성태4/10/20183124VC++: 126. CUDA Core 수를 알아내는 방법
11481정성태4/10/20184986개발 환경 구성: 357. CUDA의 인덱싱 관련 용어 - blockIdx, threadIdx, blockDim, gridDim
... 16  17  18  19  20  21  22  23  24  25  26  27  28  [29]  30  ...