Why Does Accessing a Secured Resource While Logged Out Return a 404 Page but a 200 HTTP Status Code?

Bugs
1

This topic was automatically generated from Slack. You can find the original thread here.

Very minor bug with HTTP statuses: when accessing a secured resource while logged out, the page displays a 404, but the HTTP status code is 200.

2

image.png
image.png1270×796 39.7 KB

3

image.png
image.png1686×638 72.7 KB

4

Side effect: this causes these links to be unfurled in Slack, when they shouldn’t be.

If it were a proper 404, then Slack wouldn’t unfurl it (although I can’t find the documentation for this now).

5

Example:

6

Good catch, I’ve created a quick bug report here: https://github.com/PipedreamHQ/pipedreamin/issues/6028

7

You can follow that or add additional commentary too

8

That’s a good flag — we need to improve the unfurling behavior for all our links