Question

15

cURL Received HTTP/0.9 when not allowed, but nghttp2 is installed

rated 0 times [ 15] [ 0] / answers: 1 / hits: 77696 / 3 Years ago, wed, august 18, 2021, 8:04:40

I'm trying to setup the wallet RPC for a Monero node, but when I use cURL to that port, I get this error:

curl: (1) Received HTTP/0.9 when not allowed

However, checking curl --version gives me this:

curl 7.68.0 (x86_64-pc-linux-gnu) libcurl/7.68.0 OpenSSL/1.1.1f zlib/1.2.11 brotli/1.0.7 libidn2/2.2.0 libpsl/0.21.0 (+libidn2/2.2.0) libssh/0.9.3/openssl/zlib nghttp2/1.40.0 librtmp/2.3

I thought that error would only present when cURL was compiled without nghttp2. This is an AWS environment, running 20.04.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

ibuteking

Add To Favorites

Follow

Total Points: 35

Total Questions: 128

Total Answers: 138

Location: Indonesia

Member since Thu, Oct 1, 2020

4 Years ago

ibuteking questions

1 How to hide accessibility icon?

Sat, Sep 10, 22, 08:44, 2 Years ago

1 Migrate a physical Ubuntu 20.04 Desktop to WSLg in Windows 11 by mounting the system SSD

Sat, May 28, 22, 23:27, 2 Years ago

1 What is the .var folder for in my Home Directory

Fri, May 12, 23, 10:10, 1 Year ago

1 Remove brew completely from my system

Tue, May 23, 23, 13:38, 1 Year ago

1 Ubuntu Core rotate screen Raspberry Pi 3

Sun, May 22, 22, 21:03, 2 Years ago

View All

answered 3 Years ago mugustered · Accepted Answer

It would be great to see exactly your complete curl request.
HTTP/0.9 is from 1991, previous to the basic HTTP/1.0 so I think that the problem is the response from the Server.

Please try:

Your curl command with the --verbose parameter so it outputs all the information.

Try the same URL you attempt with curl with wget and what are the contents of the file saved. Do if from inside a new empty folder.

telnet to that port and type:
```
GET / HTTP/1.0<ENTER>

<ENTER>
```
where <ENTER> is just pressing the Enter key and see the output. Maybe you are trying to open the wrong port.

Some times the problem is in the certificate. Try with the parameters:
```
--ssl

--sslv2

--sslv3
```

You can also enforce:
```
--http1.1

--http2
```

Also your organization or ISP may be using a transparent proxy which is catching the request or that is using a SSL certificate causing problems.