-
Notifications
You must be signed in to change notification settings - Fork 38
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
Support the special character '.' in header names #128
Comments
This regex is the culprit: https://github.com/AnWeber/httpyac/blob/main/src/parser/parserRegex.ts#L62. I will extend according to the RFC. |
Hey @AnWeber, thanks for the very quick reply! |
Workaround is possible using Javascript
|
That is true. |
Unfortunately Intellij does not support script or OAuth2. Otherwise the extension would not exist. I am still looking for the right regex and will then implement it. |
Thank you, much appreciated! |
Here is the fieldValueRegExp used by JSDOM: https://github.com/jsdom/jsdom/blob/master/lib/jsdom/living/xhr/XMLHttpRequest-impl.js#L34. |
@attilagyongyosi I'm sorry it took so long now after all. There was unexpectedly much movement in this project the last few days. With the new version the regex was updated and headers with |
@AnWeber, I am used to depending on enterprise teams, so no worries, this was quite a swift fix and release :) |
Background
HTTP header field names can contain the character
.
according to this RFC and the definition of atoken
within.However, httpyac fails to properly parse an
.http
file with such a header name.Although commonly used header names have dashes, certain web services can require custom header names.
httpyac
should fully support the RFC, especially for proper interoperability with the IntelliJ REST Client plugin.Example http File
Executing
httpyac
with such a file, the following error report can be observed:as the parsing of the file breaks and
header.name: xyz
is now considered as the request body.The text was updated successfully, but these errors were encountered: