-
Notifications
You must be signed in to change notification settings - Fork 29
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
Doesn't respect quoted characters #44
Comments
This is expected behavior. The slash you’re using is escaping the doublequote inside of the doubleqoute encapsulated string. Try using 3 \ characters (one more to escape the slash and another to escape the quote). |
@MikeKemmerer I would agree with you if the
but however to have to be right it should have quoted also the quote character like in:
but is uses the single quote:
Replacing the HTTP filter with HTTP output
Behaves like expected on WireMock
|
@MikeKemmerer you are right the json {"Field1": "22222wwwww\"www\"wwwwww"} is a valid json, on which the |
Logstash information:
Please include the following information:
bin/logstash --version
)8.5.1
but also tested with7.17.8
JVM (e.g.
java -version
):If the affected version of Logstash is 7.9 (or earlier), or if it is NOT using the bundled JDK or using the 'no-jdk' version in 7.10 (or higher), please provide the following information:
java -version
)JAVA_HOME
environment variable if set.OS version (
uname -a
if on a Unix-like system): anyDescription of the problem including expected versus actual behavior:
When an field of the event contains quoted characters, like
\"
the payload sent to the server should also contains the same quoting.Steps to reproduce:
Please include a minimal but complete recreation of the problem,
including (e.g.) pipeline definition(s), settings, locale, etc. The easier
you make for us to reproduce it, the more likely that somebody will take the
time to look at it.
It receives
while we would have expected
Provide logs (if relevant):
Apache http client wire logs
WireMock console
The text was updated successfully, but these errors were encountered: