Skip to content
This repository was archived by the owner on Dec 18, 2018. It is now read-only.

Access to raw headers. #160

Closed
ghost opened this issue Aug 12, 2015 · 4 comments
Closed

Access to raw headers. #160

ghost opened this issue Aug 12, 2015 · 4 comments
Labels
Milestone

Comments

@ghost
Copy link

ghost commented Aug 12, 2015

I'm wondering if there are plans on adding the ability to access raw headers in Kestrel like ALL_RAW in IIS does.

I ask because I'm building a system to detect potentially dangerous traffic and one of the metrics is based on how raw headers are delivered to the server.

This is an edge user case, so I understand if there are no plans to add this to Kestrel, and since it's open source I can add this capability myself, but I thought I would ask.

@glennc glennc added this to the Backlog milestone Aug 13, 2015
@Eilon
Copy link
Contributor

Eilon commented Aug 13, 2015

In the meantime we generally recommend putting such protections at an edge server, such as a proxy/firewall (e.g. nginx).

@ghost
Copy link
Author

ghost commented Aug 16, 2015

Thanks Eilon for your quick reply and for adding this to the backlog, it's much appreciated.

@benaadams
Copy link
Contributor

@random-username
The header values are as Raw (the string chars are values between 0-255 as per the raw bytes)

The header names capitalization are set for the pre-set group (group here https://github.com/aspnet/KestrelHttpServer/blob/dev/src/Microsoft.AspNet.Server.Kestrel/Http/FrameHeaders.Generated.cs#L16-L59)

Other header names will be set to their first occurrence capitalization if they occur more than once.

@benaadams
Copy link
Contributor

Related #594

@muratg muratg closed this as completed Jul 25, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants