curl command is not working in some curl clientscUrl for an HTTPS address/domain times out unless previously accessed from browser
What are the current battlegrounds for people’s “rights” in the UK?
Do I have to explain the mechanical superiority of the player-character within the fiction of the game?
How many people are necessary to maintain modern civilisation?
Helping ease my back pain by studying 13 hours everyday , even weekends
Is there any proof that high saturation and contrast makes a picture more appealing in social media?
Is there official documentation on directories like ~/.config and ~/.cache?
Draw a symmetric alien head
Print one file per line using echo
Can I say "I Java", or does it have to be "I do Java"?
Designing a magic-compatible polearm
What are the pros and cons for the two possible "gear directions" when parking the car on a hill?
Greeting with "Ho"
Encounter design and XP thresholds
"Correct me if I'm wrong"
Methodology: Writing unit tests for another developer
Novel in which alien (Martian?) is trapped on Earth in prehistory
Am I legally required to provide a (GPL licensed) source code even after a project is abandoned?
Can I change normal plug to a 15amp round pin plug?
I just entered the USA without passport control at Atlanta airport
Why isn't it a compile-time error to return a nullptr as a std::string?
What happened to Hopper's girlfriend in season one?
Too early in the morning to have SODA?
How did the Vostok ejection seat safely eject an astronaut from a sealed space capsule?
Is it illegal to withhold someone's passport and green card in California?
curl command is not working in some curl clients
cUrl for an HTTPS address/domain times out unless previously accessed from browser
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I was able to successfully execute curl command in Ubuntu 18.10 and some other Linux version but not in an Ubuntu 18.04 machine. The expected response is 502 but I'm getting 403 in some machines.
What is going on here?
The curl I am doing is:
curl -v -X POST https://<api>.execute-api.us-east-1.amazonaws.com/dev/invoke
It is an AWS API Gateway API serving a lambda function
Left side OpenSSL version 1.1.0g and right side OpenSSL version 1.1.1
The image below shows the failed request and successful curls respectively:
amazon-web-services curl amazon-api-gateway
|
show 5 more comments
I was able to successfully execute curl command in Ubuntu 18.10 and some other Linux version but not in an Ubuntu 18.04 machine. The expected response is 502 but I'm getting 403 in some machines.
What is going on here?
The curl I am doing is:
curl -v -X POST https://<api>.execute-api.us-east-1.amazonaws.com/dev/invoke
It is an AWS API Gateway API serving a lambda function
Left side OpenSSL version 1.1.0g and right side OpenSSL version 1.1.1
The image below shows the failed request and successful curls respectively:
amazon-web-services curl amazon-api-gateway
1
Different versions of curl/ssl libs.
– Gerald Schneider
Jun 3 at 13:26
What is the server? Does it support HTTP 2? Try running with--http1.1
...--tlsv1.2
may help too, but less likely.
– Attie
Jun 3 at 13:30
@Attie , getting 403 for both case
– Vinujan.S
Jun 3 at 13:32
1
403 is better than 502... Is the problem solved? If not, we'll need lots more information about what the server is an how you're expected to authenticate...
– Attie
Jun 3 at 13:33
1
Please add lots more detail to your question... What are you trying to do? What do you expect to see? What arguments are you passing tocurl
? What is the server? Why do you expect 502 (i.e: broken server)? etc...
– Attie
Jun 3 at 13:45
|
show 5 more comments
I was able to successfully execute curl command in Ubuntu 18.10 and some other Linux version but not in an Ubuntu 18.04 machine. The expected response is 502 but I'm getting 403 in some machines.
What is going on here?
The curl I am doing is:
curl -v -X POST https://<api>.execute-api.us-east-1.amazonaws.com/dev/invoke
It is an AWS API Gateway API serving a lambda function
Left side OpenSSL version 1.1.0g and right side OpenSSL version 1.1.1
The image below shows the failed request and successful curls respectively:
amazon-web-services curl amazon-api-gateway
I was able to successfully execute curl command in Ubuntu 18.10 and some other Linux version but not in an Ubuntu 18.04 machine. The expected response is 502 but I'm getting 403 in some machines.
What is going on here?
The curl I am doing is:
curl -v -X POST https://<api>.execute-api.us-east-1.amazonaws.com/dev/invoke
It is an AWS API Gateway API serving a lambda function
Left side OpenSSL version 1.1.0g and right side OpenSSL version 1.1.1
The image below shows the failed request and successful curls respectively:
amazon-web-services curl amazon-api-gateway
amazon-web-services curl amazon-api-gateway
edited Jun 3 at 14:51
Vinujan.S
asked Jun 3 at 13:21
Vinujan.SVinujan.S
1013
1013
1
Different versions of curl/ssl libs.
– Gerald Schneider
Jun 3 at 13:26
What is the server? Does it support HTTP 2? Try running with--http1.1
...--tlsv1.2
may help too, but less likely.
– Attie
Jun 3 at 13:30
@Attie , getting 403 for both case
– Vinujan.S
Jun 3 at 13:32
1
403 is better than 502... Is the problem solved? If not, we'll need lots more information about what the server is an how you're expected to authenticate...
– Attie
Jun 3 at 13:33
1
Please add lots more detail to your question... What are you trying to do? What do you expect to see? What arguments are you passing tocurl
? What is the server? Why do you expect 502 (i.e: broken server)? etc...
– Attie
Jun 3 at 13:45
|
show 5 more comments
1
Different versions of curl/ssl libs.
– Gerald Schneider
Jun 3 at 13:26
What is the server? Does it support HTTP 2? Try running with--http1.1
...--tlsv1.2
may help too, but less likely.
– Attie
Jun 3 at 13:30
@Attie , getting 403 for both case
– Vinujan.S
Jun 3 at 13:32
1
403 is better than 502... Is the problem solved? If not, we'll need lots more information about what the server is an how you're expected to authenticate...
– Attie
Jun 3 at 13:33
1
Please add lots more detail to your question... What are you trying to do? What do you expect to see? What arguments are you passing tocurl
? What is the server? Why do you expect 502 (i.e: broken server)? etc...
– Attie
Jun 3 at 13:45
1
1
Different versions of curl/ssl libs.
– Gerald Schneider
Jun 3 at 13:26
Different versions of curl/ssl libs.
– Gerald Schneider
Jun 3 at 13:26
What is the server? Does it support HTTP 2? Try running with
--http1.1
... --tlsv1.2
may help too, but less likely.– Attie
Jun 3 at 13:30
What is the server? Does it support HTTP 2? Try running with
--http1.1
... --tlsv1.2
may help too, but less likely.– Attie
Jun 3 at 13:30
@Attie , getting 403 for both case
– Vinujan.S
Jun 3 at 13:32
@Attie , getting 403 for both case
– Vinujan.S
Jun 3 at 13:32
1
1
403 is better than 502... Is the problem solved? If not, we'll need lots more information about what the server is an how you're expected to authenticate...
– Attie
Jun 3 at 13:33
403 is better than 502... Is the problem solved? If not, we'll need lots more information about what the server is an how you're expected to authenticate...
– Attie
Jun 3 at 13:33
1
1
Please add lots more detail to your question... What are you trying to do? What do you expect to see? What arguments are you passing to
curl
? What is the server? Why do you expect 502 (i.e: broken server)? etc...– Attie
Jun 3 at 13:45
Please add lots more detail to your question... What are you trying to do? What do you expect to see? What arguments are you passing to
curl
? What is the server? Why do you expect 502 (i.e: broken server)? etc...– Attie
Jun 3 at 13:45
|
show 5 more comments
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f969938%2fcurl-command-is-not-working-in-some-curl-clients%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f969938%2fcurl-command-is-not-working-in-some-curl-clients%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Different versions of curl/ssl libs.
– Gerald Schneider
Jun 3 at 13:26
What is the server? Does it support HTTP 2? Try running with
--http1.1
...--tlsv1.2
may help too, but less likely.– Attie
Jun 3 at 13:30
@Attie , getting 403 for both case
– Vinujan.S
Jun 3 at 13:32
1
403 is better than 502... Is the problem solved? If not, we'll need lots more information about what the server is an how you're expected to authenticate...
– Attie
Jun 3 at 13:33
1
Please add lots more detail to your question... What are you trying to do? What do you expect to see? What arguments are you passing to
curl
? What is the server? Why do you expect 502 (i.e: broken server)? etc...– Attie
Jun 3 at 13:45