# 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:** 11
**Page:** 1
### Author:  [@Hyan](https://meta.discourse.org/u/Hyan)
#### Post date: [September 20, 2023, 6:46am UTC](https://meta.discourse.org/t/get-posts-request-got-plain-http-error/279552/1 "2023-09-20T06:46:48Z")
Seems this hasn’t been reported when visiting page /posts, browsers shows. example [Discourse Meta](https://meta.discourse.org/posts)
While it should always give an application error page like what you visit [https://meta.discourse.org/posts1](https://meta.discourse.org/posts1)
---
### Author:  [@packman](https://meta.discourse.org/u/packman)
#### Post date: [September 20, 2023, 8:53am UTC](https://meta.discourse.org/t/get-posts-request-got-plain-http-error/279552/2 "2023-09-20T08:53:09Z")
I do get an error page when I follow your first link. Is it a particular browser that does this?
---
### Author:  [@Hyan](https://meta.discourse.org/u/Hyan)
#### Post date: [September 20, 2023, 9:08am UTC](https://meta.discourse.org/t/get-posts-request-got-plain-http-error/279552/3 "2023-09-20T09:08:08Z")
Tested the link in Chrome, Firefox and Safari private mode.
---
### Author:  [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [September 20, 2023, 10:03am UTC](https://meta.discourse.org/t/get-posts-request-got-plain-http-error/279552/4 "2023-09-20T10:03:53Z")
When I click the link, I also get the “oops!” page. But when I refresh that page or type the url into a new tab, then it does not work.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [September 20, 2023, 10:12am UTC](https://meta.discourse.org/t/get-posts-request-got-plain-http-error/279552/5 "2023-09-20T10:12:47Z")
It looks like it’s returning 406 error. The ember app treats it like a 404, but if you reload the browser reports it differently.
It’s an error in either case, and there are no links to that url in the ux, so it’s not clear why it’s a problem.
---
### Author:  [@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")
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.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [September 20, 2023, 1:45pm UTC](https://meta.discourse.org/t/get-posts-request-got-plain-http-error/279552/7 "2023-09-20T13:45:31Z")
> [@Hyan](#):
>
> it’s application’s responsibility to present a user friendly error message
Did the application generate the link that you are having trouble with?
Glancing at [discourse/config/routes.rb at main · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/main/config/routes.rb#1409-L1413) it doesn’t look like it’s a valid route.
~~If you start on a route that is invalid, rails isn’t going to send you the entire ember application to tell you that you have a bad URL.~~
Looks like I’m wrong, [https://meta.discourse.org/bananas](https://meta.discourse.org/bananas) loads the oops page. I guess it’s because `/posts/:id/xxx` is a valid route.
---
### Author:  [@Hyan](https://meta.discourse.org/u/Hyan)
#### Post date: [September 20, 2023, 1:57pm UTC](https://meta.discourse.org/t/get-posts-request-got-plain-http-error/279552/8 "2023-09-20T13:57:50Z")
> [@pfaffman](#):
>
> I guess it’s because `/posts/:id/xxx` is a valid route.
Yes. That how I end up with this bare /posts URL after removing the rest of parameters (but I forget where I see the /posts/:id/xxx page now). I have thought /posts is a valid route for a user’s all posts. This may be an edge case that Discourse doesn’t cover.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [September 20, 2023, 2:10pm UTC](https://meta.discourse.org/t/get-posts-request-got-plain-http-error/279552/9 "2023-09-20T14:10:30Z")
I would expect `/posts` to return all posts, but returning all posts on the system is pretty useless. You can find your posts at `https://meta.discourse.org/my/activity`
---
### Author:  [@Hyan](https://meta.discourse.org/u/Hyan)
#### Post date: [September 21, 2023, 2:01am UTC](https://meta.discourse.org/t/get-posts-request-got-plain-http-error/279552/10 "2023-09-21T02:01:31Z")
> [@pfaffman](#):
>
> but returning all posts on the system is pretty useless.
Agree with this in some degree. /posts returning empty page is this a bug of Discourse? I’m just curious if this should be, but I don’t insist on if this issue has to be fixed. Maybe it’s worthy of a further discussion from Discourse team. 🙂
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [September 21, 2023, 4:26am UTC](https://meta.discourse.org/t/get-posts-request-got-plain-http-error/279552/11 "2023-09-21T04:26:11Z")
Marking this as #pr-welcome, while valid it’s super low priority.