# GET /posts/ request got plain HTTP error

**URL:** <https://meta.discourse.org/t/get-posts-request-got-plain-http-error/279552>\
**Category:** UX\
**Tags:** pr-welcome\
**Created:** [September 20, 2023, 6:46am UTC](https://meta.discourse.org/t/get-posts-request-got-plain-http-error/279552 "2023-09-20T06:46:48Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Hyan](https://avatars.discourse-cdn.com/v4/letter/h/5fc32e/32.png) [@Hyan](https://meta.discourse.org/u/Hyan)\
**Post date:** [September 20, 2023, 1:37pm UTC](https://meta.discourse.org/t/get-posts-request-got-plain-http-error/279552/6 "2023-09-20T13:37:47Z")

</div>

Revise my question - why it returns 406 and an empty page if [Discourse Meta](https://meta.discourse.org/posts) is taken as a non exist page. 404 and an Oops message are more reasonable.

I see 406 response code from network tab in Chrome developer tools. I see a Oops page very occasionally. ~~Displaying the Oops page is reasonable.~~  
My question is no matter what errors are, it’s application’s responsibility to present a user friendly error message (like the Oops page does) rather than a blank page. I guess in case of 406 response, the application doesn’t even be reached. It’s an error reported by a service in front of application, that may be a web server or a proxy server.

---

_[View the full topic](https://meta.discourse.org/t/get-posts-request-got-plain-http-error/279552)._