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

Rename http header fields since can be both in request/response #1369

Closed
awick opened this issue Jan 30, 2020 · 1 comment
Closed

Rename http header fields since can be both in request/response #1369

awick opened this issue Jan 30, 2020 · 1 comment

Comments

@awick
Copy link
Contributor

awick commented Jan 30, 2020

Can't search fields that can be in both request/response. For example adding content-type to both request and response headers creates a single http.content-type expression and which it actually searches is unknown. Probably should create http.request.content-type and http.response.content-type or something.

Work around for now is

[custom-fields]
http.request.content-type=db:http.request-content-type;kind:termfield;count:true
http.response.content-type=db:http.response-content-type;kind:termfield;count:true

Will need to fix the http.detail.jade file up too

@awick
Copy link
Contributor Author

awick commented Feb 7, 2023

fixed in #2171

@awick awick closed this as completed Feb 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

2 participants