[bug]: 404 pages don't return 404 status code

Describe the bug

If the visitor enters a non existing URL, the network requests returns a 200 StatusCode while showing the Magento no route page. However it should return a 404 StatusCode

To reproduce

Steps to reproduce the behavior:

1. Go to venia.magento.com/venia-bottoms/venia-pants.html?page=1
2. Open your Inspect tool
3. Go to the network tab
4. Change the URL to https://venia.magento.com/venia-bottoms/venia-pantsblabkla
5. venia-pantsblabkla returns statusCode 200

Expected behavior

venia-pantsblabkla should return a statuscode 404, which would be consistent with thee 404 page shown by Magento

Screenshots

https://snipboard.io/iowkIO.jpg

Please complete the following device information:

Issue happens on all devices and all Magento PWA Studio versions

Please let us know what packages this bug is in regards to:

• venia-concept
• venia-ui
• pwa-buildpack
• peregrine
• pwa-devdocs
• upward-js
• upward-spec
• create-pwa

[vrielsa]

@anthoula even if this is expected behavior, wouldn’t it harmful for SEO scores when using PWA Studio? I cannot Imagine crawlers liking a status 200 whilst the page content clearly states its not found.

The way I understand it, is that upward resolves the route and during component render the call goes out to ResolveURL. Which, imho, is actually to late, because at that point we’d already gotten a 200. Wouldn’t it make more sense to call ResolveURL during in a middleware thats baked in upward (as far as I see upward uses express, so technically that should be possible to do)?

[azngeek]

This is def. something which is not optimal for SEO. Google might identify those pages as “soft 404” but honestly this is something which is not an expected behaviour for a crawler. Would this be in https://github.com/magento/pwa-studio/blob/develop/packages/upward-js/lib/resolvers/UrlResolver.js ?