_redirect but keep the same origin (transparent)

[martinratinaud]

Hi all

[Sorry for the weird url links but I can’t have more than 6 as I’m a new member]

I have the following:

• a wordpress blog available on exampledotcluster027dothostingdotovhdotnet
• a netlify app available on wwwdotexampledotcom

I want that

• when I hit www example com slash app I get the actual netlify app
• when I hit www example com slash * I get redirected to the blog while keeping the same url

www.example.com/blog would be a transparent redirect to example.cluster027.hosting.ovh.net/blog

Here is what I’ve tried in my _redirects file
/app/* /index.html 200
/* https://example.cluster027.hosting.ovh.net/:splat 200!

If I hit www.example.com/blog, it gets me redirected to https://example.cluster027.hosting.ovh.net/blog and what I want is to keep wwwdotexampledotcom slash blog but WITH the content of exampledotcluster027dothostingdorovhdornet slash blog

I hope I’m clear enough and that you can help me

Thanks

[luke]

Hi, @martinratinaud, and welcome to our Netlify community site.

The rule use used should have worked from what I can see. In order to troubleshoot why is isn’t working, I’ll need the actual URL at Netlify which isn’t redirecting or proxying correctly.

Or, if you prefer, you can send us the x-nf-request-id header for the request which didn’t proxy correctly.

Would you please send us either set of information above and we’ll be happy to research this further?

[martinratinaud]

Sure Luke, thanks

The website is http://remote-family.netlify.com/

and the actual website https://spot.remote-family.com

[martinratinaud]

Hey Luke do you have anyy news ?
Am I doing something wrong?

Thanks you

[luke]

Hi, @martinratinaud, I’m seeing the redirects below defined for this site:

https://spot.remote-family.com/cuisine-tendance/* https://www.<redacted>/:splat 200!
/cuisine-tendance-2/* https://www.<redacted>/:splat 200!
/test/* https://<redacted>.cluster027.hosting.ovh.net/:splat 200!
/*   /index.html   200

The first one doesn’t work because that domain (spot.remote-family.com) isn’t pointing to Netlify:

$ dig spot.remote-family.com  +noall +answer

; <<>> DiG 9.10.6 <<>> spot.remote-family.com +noall +answer
;; global options: +cmd
spot.remote-family.com.	299	IN	A	104.27.153.245
spot.remote-family.com.	299	IN	A	104.27.152.245

Those are not our IP addresses so we cannot control what that domain does. In order to use a custom domain with a Netlify site, it needs to be configured according to the instructions here for external DNS or here for Netlify DNS.

The second rule is working and the URL below proxies:

• https://remote-family.netlify.com/cuisine-tendance-2/

The third rule doesn’t work because the proxy is to an HTTPS endpoint but there is no working SSL for that URL. The URL below gives a 502 for that reason:

• https://remote-family.netlify.com/test/

Would you test changing that rule to http:// instead of https://?

The last rule is working and this proxies to index.html:

https://remote-family.netlify.com/not-a-real-file-path

I hope this helps. If there are other questions about this, please let us know.

[martinratinaud]

Hi Luke and thanks for your very detailed answer

I use cloudflare and here is my DNS entry for this subdomain

It looks like it is what is written in https://docs.netlify.com/domains-https/custom-domains/configure-external-dns/#configure-a-subdomain

or maybe I’m mistaking?

I changed the https to http

Thanks

[luke]

Are you using the Cloudflare CDN in front of Netlify? If so, this article explains about why that isn’t supported:

[Support Guide] What problems could occur when using Cloudflare in front of Netlify?

Last reviewed by Netlify Support - August, 2023 Note: We recommend not using both Cloudflare’s CDN (“Accelerate and Protect”, the orange cloud in their UI) and Netlify for the same site at the same time. Why? Read on! Netlify’s web service is not designed to work optimally with another CDN “in front of” our CDN. Proxying to our service is in general not supported and we advise you not to do it for best hosting results. Cloudflare has made similar statements that it doesn’t recommend this usa…

You can use their DNS, but please bypass their network/CDN at described in the common issue topic above. If that doesn’t resolve the issue, please let us know.

[martinratinaud]

I am indeed, thanks for pointing that out.

I will remove cloudflare and make some tests again.

Thank you for your support

[martinratinaud]

Hi and thanks for this

I

• removed cloudflare
• configured netlify DNS
• added entries to _redirects file

and it works (or almost)

It seems sometimes the _redirects file is bypassed
for example

• https://www.remote-family.com/sitemap.xml

sometimes gives the result of
https://wordpress.remote-family.com/sitemaps.xml

instead of the existing file

Is there a cache somewhere ? that can be flushed ?

Thanks again for your help

[jen]

Jumping in after a quite a bit of conversation but was wondering if you’re still experiencing this @martinratinaud?

When I go to https://www.remote-family.com/sitemap.xml in a private window in Firefox, this is what I see:

Is that correct or is the outcome you’re looking for that

• https://www.remote-family.com/sitemap.xml
  redirects to
• https://www.remote-family.com/sitemap-spot.xml?

[martinratinaud]

Hi Jen and thanks

It works now thanks

but for some time after deployment (maybe one or 2 days), the _redirects acted as if it was not here at all. Is it possible that there would be some propagation issue ?

Thanks

[perry]

Hmm, that is very strange. We are not seeing anything system-wide that should be causing behaviour like that, and without additional information its basically impossible to debug after the fact.

If you see something like that happening again, please let us know and we will try to look in to it!

[martinratinaud]

Thanks for the awesome support and the series C funding. You guys rock!

[perry]

thank you @martinratinaud! Appreciate your support.