# ResponseKit, HTTPKit's headers case sensitivity

**URL:** <https://forums.plex.tv/t/responsekit-httpkits-headers-case-sensitivity/63604>\
**Category:** Dev/API Corner\
**Tags:** other-dev\
**Created:** [April 14, 2014, 6:04pm UTC](https://forums.plex.tv/t/responsekit-httpkits-headers-case-sensitivity/63604 "2014-04-14T18:04:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![czukowski](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/czukowski/32/9008_2.png) [@czukowski](https://forums.plex.tv/u/czukowski)\
**Post date:** [April 14, 2014, 6:04pm UTC](https://forums.plex.tv/t/responsekit-httpkits-headers-case-sensitivity/63604/1 "2014-04-14T18:04:35Z")

</div>

Is this the appropriate place to report/discuss issues in Plex Framework?

&nbsp;

This one's about case sensitivity of the headers in Response and HTTP objects. According to [this document](http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2), they should be case insensitive, otherwise it may come to quite absurd situations. For example, I may want to set the cache control header:

&nbsp;

Cache-control: max-age=86400

&nbsp;

and the framework sets (somewhere in Runtime class):

&nbsp;

Cache-Control: no-cache

&nbsp;

This results in both headers set and may be interpreted by client as this:

&nbsp;

Cache-Control: max-age=86400, no-cache

&nbsp;

which won't make much sense.

&nbsp;

I suggest that Framework converts field names' case to lower in order to avoid it.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\
**Post date:** [December 21, 2019, 1:50am UTC](https://forums.plex.tv/t/responsekit-httpkits-headers-case-sensitivity/63604/2 "2019-12-21T01:50:55Z")

</div>

Closed on December 21, 2019, 1:50am UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.