Error: HPE_CB_headers_complete
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 283
- PR merge metrics
- No merged PRs in 30d
Description
I'm initilializing knox with the same key/secret/bucket that works with another library.
Then I get an object (5 bytes, text/plain) that I know exists in S3:
``` javascript
knox_client.getFile(key, function(err, kres){
if(err) return next(error(500, new Error(err)))
// ...
});
```
And I get an error. Don't know what to do next, but I have a vague suspicion this might be something about HTTPS cert incorrect or something?
```
{ [Error: Parse Error] bytesParsed: 0, code: 'HPE_CB_headers_complete' }
Error: Error: Parse Error
at ClientRequest. (/vagrant/MY_CODE.js:1:1)
at ClientRequest.emit (events.js:107:17)
at TLSSocket.socketOnData (_http_client.js:322:9)
at TLSSocket.emit (events.js:107:17)
at readableAddChunk (_stream_readable.js:163:16)
at TLSSocket.Readable.push (_stream_readable.js:126:10)
at TCP.onread (net.js:538:20)
Error: Parse Error
```
I worked around this by adding secure=false to my client, but I'd prefer to use a secure client. Is this perhaps caused by SSL certs being wrong in my vagrant box 3.13.0-45-generic ?
Contributor guide
No contributing guide indexed for this repository
Research direction
The report names the caller in /vagrant/MY_CODE.js and a Node _http_client.js stack frame; start by reproducing getFile with secure=true and comparing the endpoint and certificate behavior with secure=false. Done means identifying a repository-level cause and confirming secure-client behavior, but the issue supplies no Knox source file or test to target.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100