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.

Sign up for GitHub

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

Jump to bottom

Normalize access log Response/Request headers #163

Closed
gjdev opened this issue Apr 23, 2016 · 1 comment
Closed

Normalize access log Response/Request headers #163

gjdev opened this issue Apr 23, 2016 · 1 comment

Comments

@gjdev
Copy link

gjdev commented Apr 23, 2016

The ResponseHeadersJsonProvider and RequestHeadersJsonProvider providers create fields for every capitalisation of headers used. So you may end up with fields for 'Location', 'location', and 'LOCATION' if clients use these different capitalizations. It would be nice if there was an option to lowercase these fieldnames. That makes searches, filters, and visualisations for a specific field a lot easier.
Note that according to the HTTP protocol specs the fieldnames are case insensitive.
philsttr added a commit that referenced this issue May 1, 2016
@philsttr
For #163, add option to write request/response header names in lowerc…
f7bbfd7 
…ase for access events.

Since HTTP headers are not case sensitive, converting to lowercase will help ensure the header names
are always written to the logging event JSON in the same case.
@philsttr
Copy link
Collaborator

philsttr commented May 1, 2016

Implemented, and will be available in the next release.

@philsttr philsttr closed this as completed May 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gjdev @philsttr