Custom 404 Page by Siropu

Custom 404 Page by Siropu 1.1.7

No permission to download

Dkf

Member
Why this Add-on dosent redirect http traffic?
But https trafic redirect without problem.

How to redirect URLs like this:

Code:
https://www.domain.com/external.php?type=RSS2&forumids=1
https://www.domain.com/external.php?type=RSS2&forumids=2
https://www.domain.com/external.php?type=RSS2&forumids=3
....

to here
Code:
https://www.domain.com/forums/.1/index.rss
https://www.domain.com/forums/.2/index.rss
https://www.domain.com/forums/.3/index.rss

Thank You!!!
 
Last edited:

Tracy Perry

Well-known member
Why this Add-on dosent redirect http traffic?
But https trafic redirect without problem.

How to redirect URLs like this:

Code:
https://www.domain.com/external.php?type=RSS2&forumids=1
https://www.domain.com/external.php?type=RSS2&forumids=2
https://www.domain.com/external.php?type=RSS2&forumids=3
....

to here
Code:
https://www.domain.com/forums/.1/index.rss
https://www.domain.com/forums/.2/index.rss
https://www.domain.com/forums/.3/index.rss

Thank You!!!
It really shouldn't even be seeing any HTTP traffic. You should be doing all redirects to HTTPS at the web server level and refusing any HTTP connections.
 

Dkf

Member
It really shouldn't even be seeing any HTTP traffic. You should be doing all redirects to HTTPS at the web server level and refusing any HTTP connections.
I have redirect from HTTP to HTTPS in .htaccess
But I see HTTP requests in the log :)
 

Tracy Perry

Well-known member
I have redirect from HTTP to HTTPS in .htaccess
But I see HTTP requests in the log :)
You'll see http requests in the HTTP server logs possibly, but they should get redirected to HTTPS at the final point if they are true HTTP (web) requests. Those redirects should be occurring prior to the web application answering and XF should not be detecting any HTTP requests from outside from my understanding. The flow as the requests comes into the HTTP (not protocol) server, the HTTP server then goes "Sorry, we don't serve HTTP here, let me give you some HTTPS instead" and then passes the traffic through to the web application.
Have you confirmed that your HTTP/HTTPS redirects are working? I have come across a time or two when someone thought they were, but actually their redirects were not correct and they were serving both up. It caused issue with their user logins.
 

mazzly

Well-known member
Hi,

Is it possible to make this compatible with @mazzly 's AMP add-on? The 404 page for AMP looks broken due to the add-on.
Hmm that sounds a bit odd.. Do you have any example urls for this?

404 pages and AMP pages should be totally separate from each other unless I misremember something there 😁

We are also running this addon on our forum and haven't seen any problem with our custom 404 page in combination with AMPXF 😊
 

mazzly

Well-known member
Looking at that, it is for the AMPXF addon to fix.

However, there shouldn't exist a scenario where a user/guest would land on such a page.. (unless manually adding ?amp=1 to a 404 page)
Note: I might ofc be wrong 😁

If a user comes in through e.g. Google they will be served the cached AMP page, and at the same time googlebot will recrawl to refresh AMP page content (for next visitor), and it will then notice the 404 and stop showing the search result to other searchers since the page has disappeared..
 

JoyFreak

Well-known member
Looking at that, it is for the AMPXF addon to fix.

However, there shouldn't exist a scenario where a user/guest would land on such a page.. (unless manually adding ?amp=1 to a 404 page)
Note: I might ofc be wrong 😁

If a user comes in through e.g. Google they will be served the cached AMP page, and at the same time googlebot will recrawl to refresh AMP page content (for next visitor), and it will then notice the 404 and stop showing the search result to other searchers since the page has disappeared..
Hi,

I did drop in a message a while back in our old "Beta testing..." conversation about it and at the time, I landed on the broken 404 amp page from Google, so it's rather possible for a user/guest to land on such a page. That thread had been indexed by Google but later deleted which resulted in the broken 404 amp page. I'll bump that message so you can see for yourself. Of course that was a while a go and I'd imagine that page was deindexed on Google by now but I remember that I had deleted it a while ago and it was still serving the broken 404 amp page. So worth fixing it anyway.
 

mazzly

Well-known member
Hi,

I did drop in a message a while back in our old "Beta testing..." conversation about it and at the time, I landed on the broken 404 amp page from Google, so it's rather possible for a user/guest to land on such a page. That thread had been indexed by Google but later deleted which resulted in the broken 404 amp page. I'll bump that message so you can see for yourself. Of course that was a while a go and I'd imagine that page was deindexed on Google by now but I remember that I had deleted it a while ago and it was still serving the broken 404 amp page. So worth fixing it anyway.
That seems quite weird, but I know google indexes can be slow to update so we'll leave it at that :D

We've now release a fixed version that redirects non-200 pages to their canonical variant. :) 👍
 

Betclever

Well-known member
A bot open daily threads but a cron runs once a month to hard delete empty threads.
How to redirect hard deleted threads to the main URL?

Any SEO impact, work around IDK?

Thanks for your help🙏
 
Top