Hi Edho,
> If going so far to hit api server anyway, why not proxy all requests
> (except assets) and serve the index page if 200 and request type is
> html? nginx then can intercept errors and return correct html error
>page.
Yes, that would be possible. But – if I understand you correctly –
Hey B. R.,
Thanks for getting back to me. I am pretty sure that I was not able to make
my point very clear.
The main point is that a client accessing www.example.com/items/1 is simply
delivered a HTML file bootstrapping an AngularJS app. The JS client will
then make a separate request to
Hey B. R.,
Thanks for your reply! I will have a look at the provided resources.
As per your comment:
> I find it strange you oppose HTTP 404 with 'a proper status code': 404 is
a 'proper' status code.
> I find it even stranger you want to lie to search engines crawlers about
the existence of
Hello,
I have the following scenario:
- Client: AngularJS-based SPA running on www.example.com
- Backend: API running on api.example.com
Both live in one nginx instance in two separate "server" environments.
- Browsing to www.example.com/items/1 launches the Angular app
- App sends request to
