If I have a website that I’ve migrated to netlify called
however, there is a reservation system built with PHP that is hosted somewhere else. I found that you can create a reverse proxy url that looks like this (in _redirects):
/reservations/* https://www.not-on-netlify.com/reservations/:splat 200
I visit the
example.com/reservations and it is pulling the content from the remote site… Mind. Blown.
However - what is the catch? Is it useless in situations where the user has to login in? For example, if they log into the site will everyone else be able to see their content because netlify is caching the first user? In short - I’m trying to figure out why this looks like the solution to all my problems but will inevitably have some sort of “gotcha” that will destroy my hopes and dreams. As a side note, I thought I was going to have to create a cloudflare worker / page rule that would capture traffic from /reservations and serve it from the not-netlify site.
Thanks for any insight on the limitations of this reverse proxying stuff!