Hi,

On Tue, Aug 9, 2016, at 00:07, msonntag wrote:
> 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 api.example.com/items/1 to fetch the
> data.

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.

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx