# Is there settings with error's templates?

**URL:** <https://discourse.haproxy.org/t/is-there-settings-with-errors-templates/4908>\
**Category:** Help!\
**Created:** [February 28, 2020, 11:15am UTC](https://discourse.haproxy.org/t/is-there-settings-with-errors-templates/4908 "2020-02-28T11:15:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![riderkz](https://avatars.discourse-cdn.com/v4/letter/r/35a633/32.png) [@riderkz](https://discourse.haproxy.org/u/riderkz)\
**Post date:** [February 28, 2020, 11:15am UTC](https://discourse.haproxy.org/t/is-there-settings-with-errors-templates/4908/1 "2020-02-28T11:15:28Z")

</div>

In old version of haproxy 1.8 was

```auto
HTTP/1.1 302 Found
Location: https://localhost/

```

In new version 2.1 it is

```auto
HTTP/1.1 302 Found
location: https://localhost/

```

with “l” in lowercase

Is it possible to revert it back to Uppercase “L”?

---

<div class="post-metadata">

**Author:** ![lukastribus](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lukastribus](https://discourse.haproxy.org/u/lukastribus)\
**Post date:** [February 28, 2020, 6:55pm UTC](https://discourse.haproxy.org/t/is-there-settings-with-errors-templates/4908/2 "2020-02-28T18:55:02Z")

</div>

If you have a bogus client that breaks otherwise, yes, you can workaround this client bug with the bogus client features that have been introduced for this use-case. Something like:

```
global
 h1-case-adjust location Location
default
 h1-case-adjust-bogus-client

```

Also see [h1-case-adjust](https://cbonte.github.io/haproxy-dconv/2.0/configuration.html#3.1-h1-case-adjust) and [option h1-case-adjust-bogus-client](https://cbonte.github.io/haproxy-dconv/2.0/configuration.html#4.2-option%20h1-case-adjust-bogus-client).

---

<div class="post-metadata">

**Author:** ![riderkz](https://avatars.discourse-cdn.com/v4/letter/r/35a633/32.png) [@riderkz](https://discourse.haproxy.org/u/riderkz)\
**Post date:** [April 21, 2020, 2:48pm UTC](https://discourse.haproxy.org/t/is-there-settings-with-errors-templates/4908/3 "2020-04-21T14:48:00Z")

</div>

Thank you! Works fine now.