Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HPE_INVALID_CONSTANT error with request module #49

Closed
girishbr opened this issue Mar 27, 2014 · 2 comments
Closed

HPE_INVALID_CONSTANT error with request module #49

girishbr opened this issue Mar 27, 2014 · 2 comments
Labels
Milestone

Comments

@girishbr
Copy link

Using request module to delete an entity on a customer opdk. Works fine on V8. But with Trireme it dumps with
error { [Error: Parse Error] message: 'Parse Error', code: 'HPE_INVALID_CONSTANT' }
TypeError: Cannot read property "statusCode" from undefined.

This gist https://gist.github.com/girishbr/4378ce246f9ee579a8b2 contains the traces. Please look.

@gbrail gbrail added the bug label Mar 28, 2014
@gbrail gbrail added this to the 0.7.2 milestone Mar 28, 2014
@gbrail
Copy link
Contributor

gbrail commented Mar 28, 2014

The issue is that one of the API calls was returning the following HTTP status line:

"HTTP/1.1 413 "

Note the extra space at the end.

Trireme wasn't anticipating that (and it's dubious whether it's allowed by RFC2616) but at any rate it's fixed in the current snapshot.

@gbrail
Copy link
Contributor

gbrail commented Mar 28, 2014

Fixed in 0.7.2.

@gbrail gbrail closed this as completed Mar 28, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants