You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My Laravel app is a backend API server for SPA (Single page app).
While the SPA is in server side rendering, it accesses Laravel through AWS Network Load Balancer(L4 Load Balancer), but NLB's protocol and host name is http://my-app-nlb-12345.elb.region.amazonaws.com. Therefore, a paginator returns URLs(next_page_url etc) with NLB's protocol and host name.
How can I fix the protocol and host name of paginator URLs?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
My Laravel app is a backend API server for SPA (Single page app).
While the SPA is in server side rendering, it accesses Laravel through AWS Network Load Balancer(L4 Load Balancer), but NLB's protocol and host name is
http://my-app-nlb-12345.elb.region.amazonaws.com
. Therefore, a paginator returns URLs(next_page_url
etc) with NLB's protocol and host name.How can I fix the protocol and host name of paginator URLs?
Beta Was this translation helpful? Give feedback.
All reactions