August 08, 2016 12:59PM
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 – my backend would then need to serve the index page itself, and therefore be highly coupled to the frontend.

Currently, my backend does not have any knowledge about the frontend whatsoever.

Thanks for your input.
Subject Author Posted

Return proper status codes (404, 302) from client-side Single Page Application

msonntag August 08, 2016 05:50AM

Re: Return proper status codes (404, 302) from client-side Single Page Application

B.R. August 08, 2016 06:06AM

Re: Return proper status codes (404, 302) from client-side Single Page Application

msonntag August 08, 2016 06:15AM

Re: Return proper status codes (404, 302) from client-side Single Page Application

B.R. August 08, 2016 10:44AM

Re: Return proper status codes (404, 302) from client-side Single Page Application

msonntag August 08, 2016 11:07AM

Re: Return proper status codes (404, 302) from client-side Single Page Application

Edho Arief August 08, 2016 11:18AM

Re: Return proper status codes (404, 302) from client-side Single Page Application

msonntag August 08, 2016 12:59PM

Re: Return proper status codes (404, 302) from client-side Single Page Application

Edho Arief August 08, 2016 01:04PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 182
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready