Rewrite with proxy gives 404 with Nuxt On SPA , But works when refreshing with the same URL

Support
,
1

Am trying to make a rewrite using proxy to my another netlify instance from my deploy url, it does work with refresh but not when navigate through browser as SPA gives 404 , have a look at my redirect rule , can anyone please help to rewrite with same url to my another instance ?

DeployURL : https://deploy-preview-260--slim-staging.netlify.app , Click this url and try hitting on menu learn on nav bar that will through a 404 error but when u refresh the page loads with some content loading errors

image
image1205×470 66.8 KB

Framework : Nuxt 2 with Static Site Generator

Case: I need to fetch blogs from secondary netilfy instance when user hits on blog in primary website or main domain

[[redirects]]
force = true
from = "/blog/*"
status = 200
to = "https://v3-staging-orphan.netlify.app/blog/:splat"
2

I tested this now and your website appears to wokring fine. Is this resolved?

3

No look how the page loads , its refreshing (Clicking on the page reload the whole page by refreshing ) not working as SPA , its tweak we have added for to work , is there any way to avoid the refresh and work as SPA ?

4

Is there a deploy in which the page was loading as an SPA and was failing that we can check?

5

Yeah i have opened a NEW PR for you guys to test , try this URL , click on blogs you will get the 404 page from primary webiste

6

Hi, @focaloid-dev. There isn’t a “blogs” link on the page but there is a link for “blog” which has this URL associated with it:

https://deploy-preview-264--slim-staging.netlify.app/blog

However, when I test that link it is a 200 status response:

$ curl -H "Accept-Encoding: br, deflate, gzip" -svo /dev/null --stderr - https://deploy-preview-264--slim-staging.netlify.app/blog  | egrep '^(<|>)'
> GET /blog HTTP/2
> Host: deploy-preview-264--slim-staging.netlify.app
> User-Agent: curl/8.1.2
> Accept: */*
> Accept-Encoding: br, deflate, gzip
>
< HTTP/2 200
< age: 0
< cache-control: no-cache
< content-encoding: br
< content-type: text/html;charset=utf-8
< date: Tue, 26 Sep 2023 23:30:41 GMT
< server: Netlify
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< vary: Accept-Encoding
< x-nf-request-id: 01HB9X979M4R559P2N3CSNRYX3
< x-powered-by: Nuxt
<

We really need to see the error to be able to troubleshoot. It is nearly impossible to troubleshoot an error that we cannot reproduce and don’t have any more information about.

There are two things that might help us. Would you be willing to please do one of the two things below?

  • send us an example curl command that will reliably trigger the 404
  • make a HAR recording of the 404 occurring and post that HAR file here

With that information, we should be able to move the troubleshooting of this issue forward. As it stand now, though, we cannot even see the error so we cannot even begin to debug it.

7

Thanks for the responce , i can see that the network tag is not showing any 404 errors while we navigate through the browser , it simply shows the 404 in the browser view , i dont know whether that is a framework related error since you have posted 200 status response and there isnt a link as blogs thats a typo from my side am sorry ! , i might think if you click on blog as SPA mode , it shows a 404 for u too ? , but if u paste over the url directly in the browser and hit enter we get to load from the content from second website and its a success in that case !

8

HI, @focaloid-dev. I do not see a 404 in the browser either. I cannot reproduce the error you are seeing. This is why I asked for one of the two piece of information below:

  • send us an example curl command that will reliably trigger the 404
  • make a HAR recording of the 404 occurring and post that HAR file here

If you are willing to send us that information, please reply here anytime.

You can post that information publicly or you can private message (PM) that to one of our support staff. I’ve confirmed that PMs are enabled for your forum login. Please keep in mind that only one person can see the PM and this will likely mean a slower reply than posting the information publicly. Please feel free to reply to however you prefer though.