Error parse error expected http

Parse Error: Expected HTTP/ #662

Version: 1.48.0 (system setup)
Commit: db40434f562994116e5b21c24015a2e40b2504e6
Date: 2020-08-13T07:50:42.600Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363

Steps to Reproduce:

Using a get request saved in a send.http file (GET http://url HTTP/1.1) it now shows a Parse Error: expected HTTP/

Using a POST, PUT or DELETE to the same local URL does work normally.

This is since the update of vscode to 1.48
With 1.47.x there was no issue at all.

The text was updated successfully, but these errors were encountered:

@JohnPiepersSmits could you please show me your actual request or HTTP file

But if I try a GET to the same local url:
GET http://website.local/dev/api.php

This shows the popup with the Parse Error: expected HTTP/

As I already mentioned, this error is since VSCode was updated to version 1.48
Before that there was no issue at all.

@JohnPiepersSmits could you please show me the error details, you can checkout this in the output channel of REST

Sure, I have made a screenshot

I have the same error. Below is the error from the output terminal for the RESTClient extension.

Источник

Parse Error: Expected HTTP/ #38

On mockttp 0.20.0, 0.20.1, and 0.20.2 I get a weird http parse error. I think it is something to do with response encoding.

Node version is 12.18.0

tested the request with request-promise, axios, and fetch with the same results each time

The text was updated successfully, but these errors were encountered:

This error comes directly from Node’s HTTP parser, try searching for HPE_INVALID_CONSTANT in here: https://github.com/nodejs/http-parser/blob/master/http_parser.c.

It is possible that Mockttp somehow interferes with the data that node’s receiving, but it’s unlikely. This is probably a real problem with the request itself (or the response, if you’re proxying this traffic to a real server).

Can you share the code that’s sending the request?

You could also try making the same request manually through HTTP Toolkit, which will show the same error but hopefully with more context, or Wireshark (if it’s not HTTPS).

I see, the code still works when you are making requests to the actual http server so I think it could be that unlikely scenario 😨

On mockttp 0.19.3 the code works.

The client we are calling the api with looks like

data is just an object and the axios version is 0.19.2
I am downloading the http toolkit now to get more info

What does your Mockttp mocking code for this request look like?

One guess: are you mocking the response headers here? What happens if you add «Transfer-Encoding»: «chunked» to those?

In Mockttp headers property for your mock then you take responsibility for specifying all response headers. To make your response body valid, you might need either a chunked encoding or a content-length valid. That sounds like it might cause this kind of thing.

We do not specify headers but we are using .thenJSON to send our responses.

Here is the issue in http parser that could be causing this.

I will try the «Transfer-Encoding»: «chunked» suggestion and if it works make a PR to add this to thenJson this afternoon

With that header I get this error

I also noticed its only happening with axios, not node-fetch. Unless you have a better suggestion I can raise the issue there.

axios sets a content-length header in the request, is that relevant?

TBH I don’t fully understand whats going on 🤷‍♂️

Ok, I think I’ve worked out the root cause of this, it is indeed a Mockttp bug. This code by itself fails with the «Parse Error: Expected HTTP/» error you describe:

If you replace the emoji in id with «123» it doesn’t fail any more.

I think what’s happening here is that thenJSON is calculating the content length for you (here), assuming everything is ASCII, and that’s causing errors with unicode content like this.

Then because the content length is wrong, some of the content is treated by the HTTP client as part of a subsequent unexpected response, except it’s really the end of the response body, so it doesn’t parse.

Make sense? In the short term you can fix it by avoiding unicode, or specifying your own headers property for thenJSON with a corrected Content-Length header value. I’ll look into it and get a proper fix for you though, shouldn’t take too long.

Ok, I think the version I’ve just pushed now fixes this. If you’ve got a minute, could you please:

• Clone this repo, and in that folder:
  • npm install , npm run build , npm link
• In your project:
  • npm link mockttp
  • Run your tests, and see if this fixes your issue

Nooo emoji life why did you cause me pain 😂 😂 😂 😂 😂

Thanks so much for this, I will test it out first thing in the morning 🥰

It works! thank you 🙂

Great! Thanks for testing that. I’ll put together a proper release in the next day or so, so you can use this for real, watch this space.

This was just published as v0.20.3 🎉 .

Thanks for reporting this. Hope that sorts things out for you, let me know if you have any other trouble.

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Common Errors and Warnings​

This page lists common error and warning messages that you might find in CriblВ Stream’s internal logs and/or UI. It includes recommendations for resolving the errors/warnings. Messages are grouped by component (Sources, Destinations, etc.). Note that:

We’ve excerpted only the salient part of the error message from each event. We haven’t listed full events.

Examples don’t preserve case sensitivity from the original events.

NodeJS serves as the CriblВ Stream backend and has a large collection of well documented errors of its own. Some of system-level are listed below with the appropriate action to take. The remainder are documented at https://nodejs.org/docs/latest-v14.x/api/errors.html#errors_node_js_error_codes, specifically in the Common system errors section of that page.

Where events are written to log files, they might reside in different logs variously devoted to dataВ processing, cluster communication, or the REST API. (For details, see Types of Logs.) We note the log type where necessary.

Web UI​

Where: In CriblВ Stream’s UI.

Error: «Failed to fetch»вЂ‹

Cause: This occurs only when accessing Data > Collectors. It can occur with ad blockers, and occurs with the Brave browser (because the newly loaded page’s URL includes the string collector ).

Recommendation: If you have an ad blocker, allowlist the https:// :9000/jobs/collectors (single-instance) URL or the https:// :9000/m/ /jobs/collectors (Leader) URL.

Error: «The Config Helper service is not available because a configuration file doesn’t exist or the settings are invalid. Please fix it and restart CriblВ Stream.»вЂ‹

Cause: Occurs only on Leader Nodes. Each WorkerВ Group relies on a config helper process that runs on its behalf on a Leader Node, and that process is not currently running. This error is usually triggered by restarting CriblВ Stream on the LeaderВ Node, and then trying to access one of these UI features before the CriblВ Stream server is fully up:

• Groups or Configure link (3.x).
• WorkerВ Groups menu (2.x).
• ManageВ >Groups or ManageВ >Workers tabs (4.x).

Recommendation: Try again in a few seconds. If you’ve made changes to the backend or filesystem permissions, stop CriblВ Stream, and make sure the cribl user owns all relevant assets, before restarting: sudo chown -R cribl.cribl /opt/cribl

Warning: «KMS saved, but secret exists in destination location. No data migrated.»вЂ‹

Cause: This will appear when you attempt to save KMSВ Settings with a SecretВ Path entry that references a secret that already exists in HashiCorp Vault. It can also occur with OpenIDВ Connect remote authentication. CriblВ Stream has aborted the remote write to avoid overwriting an external shared secret.

Recommendation: On the Leader Node, manually edit kms.yml to use provider:В local . Then restart CriblВ Stream to correct the path conflict.

Sources (General)​

Where: These events will be in the Worker process logs.

Error: «bind EACCES 0.0.0.0:514″​

Cause: CriblВ Stream doesn’t have proper privileges to bind to the specified IP and port. Usually, this simply indicates that CriblВ Stream is running as a non-root user, but a Source was accidentally configured to use a privileged port below 1024.

Recommendation: Check your CriblВ Stream Sources’ configuration. The error’s channel field will indicate which input is affected. If you choose to enable access to the port range below 1024, see our configuration instructions for systemd and initd.

Error: “bind EADDRINUSE 0.0.0.0:9514”​

Cause: The interface and port combination is already in use by another process, which might or might not be CriblВ Stream.

Recommendation: Check your CriblВ Stream Sources’ configuration. The error’s channel field will indicate which Source is affected, but this error means that one or more other inputs are also using the same IP/port combination.

HTTP-based Source​

Where: These events will be in the Worker Process logs.

Message: «Dropping request because token invalid»,»authToken»: «Bas. Njc=»» (v2.4.5 and later)​

Cause: The specified token is invalid. Note the above message is logged only at debug level.

Kafka-based Source​

Where: These events will be in the Worker Process logs.

Cause: The username does not have read permissions for the specified topic.

Splunk TCP Source​

Where: These events will be in the Worker Process logs.

Error: «connection rejected» with a reason of «Too many connections»вЂ‹

Cause: The maximum number of active Splunk TCP connections has been exceeded per worker process. The default is 1000.

Recommendation: In the Splunk TCP input’s Advanced Settings configuration, increase the Max Active Connections value, set it to 0 for unlimited, and/or increase the # of worker processes the Worker Node(s) are using..

Splunk HEC Source​

Where: These events will be in the Worker Process logs.

Error: «Malformed HEC event»вЂ‹

Cause: The event is missing both event and fields fields.

Error: «Invalid token»вЂ‹

Cause: Auth token(s) are defined, but the token specified in the HEC request doesn’t match any defined tokens, therefore it’s invalid.

Error: «Invalid index»вЂ‹

Cause: The Splunk HEC Source’s Allowed Indexes field is configured with specific indexes, but the client’s HTTP request didn’t specify any of them.

Error: «<«text»:»Server is busy»,»code»:9,»invalid-event-number»:0>«вЂ‹

Note: This is not logged in CriblВ Stream, but would be found in the response payload sent to your HEC client.

Cause: «Server is busy» is the equivalent of a 503 HTTP response code. The most likely cause is the Max active requests setting in the HEC input’s Advanced Settings is insufficient to service the number of simultaneous HEC requests. Increase the value and monitor your clients to see if the 503 response is eliminated.

TLS Errors​

Where: These events can be in Worker Process or API logs on the Workers or Leader, depending on whether the issue is associated with a Source or Destination, etc.

Error: “certificate has expired”​

Cause: Validate server certs or Validate client certs is enabled, and the peer’s certificate has expired.

Recommendation: Disable Validate server certs or Validate client certs (depending on whether CriblВ Stream is serving as the client or server), so that encryption can still occur without authentication. Or renew the expired certificate.

Error: “Client network socket disconnected before secure TLS connection was established”​

Cause: Typically caused by a TLS protocol version mismatch between the client and server.

Recommendation: Verify that client’s and server’s TLS settings use the same minimum/maximum TLS version.

Error: “Unable to get local issuer certificate”​

Cause: Client can’t validate the server certificate’s CA (i.e., the issuer) because it doesn’t trust the CA cert. Or vice versa (server can’t validate client’s certificate CA) if mutual auth is enabled.

Recommendation: The CA certificates used by the server’s leaf certificate must be trusted by the client. See Configuring CA certs.

Error: “self signed certificate”​

Cause: The client or server was presented with a self-signed cert from the peer, but that cert is not trusted.

Recommendation: The self-signed certificate must be trusted by the peer to which it’s presented. See Configuring CA certs.

Error: “Hostname/IP does not match certificate’s altnames»вЂ‹

Variations: “Hostname/IP does not match certificate’s altnames: host: is not in the cert’s list” or: “Hostname/IP does not match certificate’s altnames: IP: is not in the cert’s list”

Cause: The server’s hostname/FQDN used on the client is not found in the CN or SAN attribute of the server’s certificate.

Recommendation: Examine the CN and/or SAN attribute, to see which names are listed that can be used as the server hostname/FQDN on the client. CN values with spaces are not supported as hostnames/FQDNS. If there isn’t a SAN attribute, then a new cert will need to be issued.

Error: «140244944713600:error:141E70BF:SSL routines:tls_construct_client_hello:no protocols available:»вЂ‹

Cause: The highest TLS protocol available by the client is still too low for the server to support.

Recommendation: Review the minimum/maximum TLS version settings on the client and server, to ensure that they overlap.

Error: «140251374995328:error:1408F10B:SSL routines:ssl3_get_record:wrong version number»вЂ‹

Cause: The client is using TLS but the server is probably not configured for TLS.

Recommendation: Review the TLS settings on the server.

REST API Collector​

Where: These events will be in the Worker Process logs.

Error: «reason.stack == `TypeError [ERR_INVALID_URL] : Invalid URL: https%3A%2F%2Ftype.fit%2Fapi%2Fquotes» at onParseError (internal/url.js:258:9)»вЂ‹

Cause: This is due to unnecessarily encoding the Discover/Collect URL.

Recommendation: Remove the encoding function for the URL. URLs will rarely need text be encoded and when they do it’s only the parts that need it that should be encoded, otherwise if the entire URL is encoded unnecessarily then errors like this will occur.

Error: «statusCode: 429. Too many requests»вЂ‹

Cause: This response is triggered by rapidly repeated authentication requests from the Collector’s Discover and Collect phases. It’s especially likely when different Workers run multiple Collect tasks.

Recommendation: Navigate to Settings > General > Advanced and gradually increase the LoginВ Rate Limit until this error response is no longer returned.

AWS Sources/​Destinations & S3-Compatible Stores​

Where: These events will be in the Worker Process logs.

Error: «message»:»Inaccessible host: ‘sqs.us-east-1.amazonaws.com’. This service may not be available. «вЂ‹

Full Error Text: «message»:»Inaccessible host: ‘sqs.us-east-1.amazonaws.com’. This service may not be available in the ‘us-east-1’ region.»,»stack»:»UnknownEndpoint: Inaccessible host: ‘sqs.us-east-1.amazonaws.com’. This service may not be available in the ‘us-east-1’ region.

Cause: If this is persistent rather than intermittent then it could be caused by TLS negotiation failures. For example, AWS SQS currently does not support TLS 1.3. If intermittent then a network-related issue could be occurring such as DNS-related problems.

Error: «Missing credentials in config» or «stack:Error: connect ETIMEDOUT 169.254.169.254:80″​

Cause 1: Can occur when Authentication is set to Auto, but no IAM role is attached.

Cause 2: Can occur on LogStream 2.4.4 or earlier, when an IAM role is attached to the EC2 instance, but the instance is using instance metadata v2.

Recommendations: Change to Manual Authentication; attach an IAM role; or if using IMDv2, switch to IMDv1 (ifВ possible) or upgrade to LogStream 2.4.5 or later.

Destinations (General)​

Where: These events will be in the Worker Process logs, unless otherwise noted.

Warning: “sending is blocked”​

Cause: The Destination is blocking. This can occur with any TCP-based Destination, and is logged only after 1 second of blocking. This can also occur between Worker and Leadr when the Worker can’t connect to the Leader Node to send metrics data. When triggered by cluster communication, the warning will be in the Worker’s API log.

Warning: «exerting backpressure» (v2.4.0-2.4.1)​

Cause: The Destination is blocking. This message is logged immediately upon detecting backpressure, for Destinations using any protocol. Some backpressure is normal when measured over timescales under 1В second, therefore this message can appear quite frequently, and is not indicative of a problem (which is why it’s a warning).

Warning: «begin backpressure» and «end backpressure» (v2.4.2 and later)​

Cause: The Destination is blocking. Like the «sending is blocked» message, «beginВ backpressure» is logged only after 1 second of blocking. Unlike the «exertingВ backpressure» message, it is logged only once while backpressure is occurring (at the start), and it will always be followed by the «end backpressure» message.

MinIO Destination​

Where: These events will be in the Worker Process logs.

Error: «Parse Error: Expected HTTP/»вЂ‹

Cause: The Worker is trying to use HTTP, but the server is expecting HTTPS.

Pipelines/Functions​

Where: These events will be in the Worker Process logs.

Error: «failed to load function. Value undefined out of range. «вЂ‹

Cause: A LookupВ Function attempted to load a lookup table that exceeded Node.js’ hard size limit of 16,777,216 (i.e., 2 24 ) rows.

Recommendation: Split the lookup table to smaller tables, or use the RedisВ Function.

Diag Command​

Where: On stdout

Warning: «You are running CriblВ Stream CLI as user=root, while the binary is owned by the user=cribl.»вЂ‹

Full Text: «WARNING: You are running CriblВ Stream CLI as user=root, while the binary is owned by the user=cribl. This may change the ownership of some files under CRIBL_HOME=/opt/cribl. PleaseВ make sure all files under CRIBL_HOME=/opt/cribl are owned by the user=cribl.»

Cause: This is caused by improper ownership on $CRIBL_HOME , and will cause some files to be missing from the diag.

Recommendation: Execute the chown command on the entire $CRIBL_HOME directory, so that everything can be owned by the proper user. Afterward, run the ./cribl diag create command again.

Cluster​

Where: These events will be in the Workers’ API logs.

Источник

Я управляю приложением, созданным третьими сторонами на python.

У меня есть этот диспетчер URL

urls += [(r'/path/objectA/(.*)', ObjectAHandler)]  # this was made by third parts, it is expected to work

И этот класс

class ObjectAHandler(BaseHandler):

    def __init__(self, application, request, **kwargs):
        super(ObjectAHandler, self).__init__(application, request, **kwargs)  # do the init of the basehandler

    @gen.coroutine
    def post(self, action=''):
        response = {}
        
            ...     
            
            response = yield self.my_method(json_data)
        
            ... 

        self.write(json.dumps(response))

    def my_method(self, json_data)
        ...

Я хочу проверить, что приложение правильно получает запрос и возвращает какой-то ответ.

Поэтому я пытаюсь получить доступ к этому URL-адресу с помощью Postman

Тип запроса:

POST

URL:

http://<machine_ip>:<machine_port>/path/objectA/

Я получаю эту ошибку из окна ответа почтальона

Ошибка синтаксического анализа: сервер вернул искаженный ответ

И когда я нажимаю «просмотреть в консоли», я вижу

POST http://machine_ip>:<machine_port>/path/objectA/
Error: Parse Error: Expected HTTP/
Request Headers
Content-Type: application/json
User-Agent: PostmanRuntime/7.28.4
Accept: */*
Postman-Token: d644d7dd-699b-4d77-b32f-46a575ae31fc
Host: xx.xxx.x.xx:22
Accept-Encoding: gzip, deflate, br
Connection: keep-alive
Request Body

Что означает Error: Parse Error: Expected HTTP/?

Я проверил журналы своего приложения, но, похоже, оно не обрабатывает ни один запрос, даже если Почтальон указывает, что сервер возвращает (искаженный) ответ.

Я также попытался изменить целевой URL-адрес на:

https...

Но он возвращается

 Error: write EPROTO 28427890592840:error:100000f7:SSL routines:OPENSSL_internal:WRONG_VERSION_NUMBER:../../third_party/boringssl/src/ssl/tls_record.cc:242:

Который я обнаружил это указывает на то, что я должен придерживаться HTTP

Затем я также попробовал:

http://<machine_ip>/path/objectA/

А также

<machine_ip>/path/objectA/

Которые обычно возвращают:

Error: connect ECONNREFUSED <machine_ip>:80

Я также попытался заменить строку

urls += [(r'/path/objectA/(.*)', ObjectAHandler)]  

С участием

urls += [(r'/path/objectA/', ObjectAHandler)]  

А также

urls += [(r'/path/objectA', ObjectAHandler)]  

Но ничего из этого не сработало.

Что не так? Как я могу это исправить?

ОБНОВИТЬ

По-видимому, согласно этой ветке на Postman Github, проблема возникает только на рабочем столе Postman, а не на Postman в браузере.

Итак, я попытался отправить форму запроса Postman в своем браузере, но я получаю

 Cloud Agent Error: Can not send requests to reserved address. Make sure address is publicly accessible or select a different agent.

Потому что, согласно этой другой теме,

Веб-сайт Postman не может отправить запрос на локальный хост вашего компьютера. Сначала необходимо подключиться к вашему ПК с настольным клиентом Postman.

И даже если я буду следовать указаниям в этом ответе

Запустите его [ndr. Рабочий стол Postman], затем перейдите в рабочее пространство Postman в браузере -> отправьте запрос, и он будет работать.

Я все еще получаю то же самое

Error: Parse Error: Expected HTTP/

Как в Postman Desktop, так и в Postman в браузере.

ОБНОВИТЬ

Продолжая отладку, я попытался свернуть этот URL-адрес со своего терминала:

myuser@mymachine-VirtualBox:~$ curl --verbose "http://<target_machine_ip>:<target_machine_port>/path/objectA"

И я получил:

*   Trying <target_machine_ip>:<target_machine_port>...
* Connected to <target_machine_ip> (<target_machine_ip>) port <target_machine_port> (#0)
> GET /orkpos5/receipt HTTP/1.1
> Host: <target_machine_ip>:<target_machine_port>    
> User-Agent: curl/7.74.0    
> Accept: */*    
>     
* Received HTTP/0.9 when not allowed  
    
* Closing connection 0    
curl: (1) Received HTTP/0.9 when not allowed