Yes. Me too. Just recently it does.
Btw, I am using nginx, SSL (Let’s Encrypt) and Cloudflare as DNS Manager.
-
This reply was modified 9 years, 5 months ago by
RiseCakoPlusplus. Reason: add extra info
I know the OP had luck with Meta Refresh in the Pro version. Our 2.0.0 release is getting close and has a number of performance improvements as well.
However, the 30x redirects “should” be the fastest redirect types, unless the nginx proxy is causing some delays.
Thread Starter
brunomp
(@allanmcbilly)
I’m using a very similar configuration RiseCako: nginx+ssl+cloudflare.
Perhaps there’s something there?
Yeah I changed to meta refresh with the pro version and now redirect times are doing fine. But it’s still odd. Cause like you said: 30x SHOULD be faster than a mete refresh redirect.
There’s only two users who reported here about this, but perhaps some kind of problem between nginx+ssl+cloudflare with pretty link?
I’d prefer using straight up 30x.
I’ve tried the new 2.0 as well and that didn’t solve the problem with 30x redirects.
So for now I’ll keep the old version 🙁
Thanks!
If your Webhost is using nginx, there’s a very good chance that it’s an nginx/apache hybrid setup.
Cloudflare uses nginx also and sits as a proxy for cached requests before the webhost.
So with a 30x redirect the following may be happening during a typical request.
Browser -> Cloudflare proxy -> Webhost nginx -> Apache -> WordPress/Pretty Link -> back to Webhost nginx -> back to Cloudflare proxy -> back to Browser.
So there’s possibility for a lot more latency there.
With meta refresh redirects, Cloudflare may actually be caching those as it returns some HTML output. So the route would be:
Browser -> Cloudflare proxy -> back to Browser.
In this scenario WordPress would not get invoked at all, which is why the meta refresh would be redirecting much quicker. The downside here is that your tracking (hits/clicks) would not be accurate unless you use something like Google Analytics to track them instead.
Thread Starter
brunomp
(@allanmcbilly)
Hummm I see. That indeed makes sense. I’ll check with my guys to see if we can confirm that and what we can do about it.
We could disable cloudflare’s proxy and CDN I think… but then we might lose some speed, not sure.
Thanks Paul! Appreciated!
Pretty Link 2.0.0 will have a new base slug prefix feature. You could use this to add /go/ or /out/ or anything else to the front of your pretty links (doesn’t affect existing links though).
It’s been awhile since I used cloudflare, but I thought there was a way to define a page rule that will force them to cache any URL’s matching that rule.
If so, then you could force Cloudflare to cache your 30x’s by setting up a page rule for /out or /go etc.
Again though, this would mean your hits tracking is off due to the cache bypassing WordPress.
