# Feature Request: Legacy HTTP Support

**URL:** <https://meta.discourse.org/t/feature-request-legacy-http-support/73375>\
**Category:** Feature\
**Created:** [November 3, 2017, 6:03pm UTC](https://meta.discourse.org/t/feature-request-legacy-http-support/73375 "2017-11-03T18:03:44Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![nsuchy](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nsuchy/32/166530_2.png) [@nsuchy](https://meta.discourse.org/u/nsuchy)\
**Post date:** [November 3, 2017, 6:03pm UTC](https://meta.discourse.org/t/feature-request-legacy-http-support/73375/1 "2017-11-03T18:03:44Z")

</div>

I have a feature request. I have a hardware appliance that runs in-line with my webserver. When activated it intercepts HTTP and HTTPS requests. The problem being it does not support HTTP/2 or WebSockets. When it’s activated certain actions like post edits fail to complete. It’s only activated during DDoS Attacks using HTTP/HTTPS floods (it won’t activate in the case of a syn flood that’s handled differently) however legacy support for HTTP/1.1 without WebSockets would be a nice enhancement useful for websites that are under attack. Thoughts?

---

_[View the full topic](https://meta.discourse.org/t/feature-request-legacy-http-support/73375)._
