Internet explorer not finding right content from wordpress multisite - wordpress

Okay, so this is at weird one. I only encounter this issue in IE and no other browser.
I have a wordpress multisite installation where I have content on: example.com and example.com/sub-installation
So there is a front page when a user accesses: example.com/sub-installation
The front page does show up when you access it. However, the content of that page is supposed to change if the user is logged in. SOMETIMES that content won't change when the user is logged in.
When I click F12 and check the Network tab, it seems like the issue occurs because the browser tries to access a sub-page to example.com and not example.com/sub-installation:
issue
When it looks like this the page works as intended:
fixed
Is there a way to prevent this?
Does anybody know why it only does this sometimes?
I figure that I could just change the URL for the sub-installation, but is there anything else or?
*edit
So, I see that the likely reason I because Internet Explorer is hit with a 304 redirect trying to access a sub-page to the example.com installation, whereas every other browser is hit with a 301 redirect and thus tries to access the sub-installation instead....
Does anybody know why Internet Explorer is the only one receiving a 304?
And what can I do to prevent this?

So this is in no way the best solution, but it seems like the issue in Internet Explorer occurs when the browser is trying to access just the URL: example.com/sub-installation
When I simply add a slash to the end of it, the browser will try to access the front page on example.com/sub-installation and not try to access a sub-page to example.com.
It doesn't really solve the issue for good, but it works for now....

Related

Disable favicon.ico request in wordpress based site

I'm using twentytwentytwo theme. When I open the page, it performs 2 requests to favicon.ico. How can I completely disable favicon.ico request in wordpress based site? Do we have any htaccess setting for this?
all it means is that people with browsers that use favicon (Internet Explorer 5.0 +, Firefox, Opera and a most others) are visiting your site. While seeing a 404 in your log files usually means that a visitor got the dreaded "404 Page Not Found" error, in this case it doesn't. All it means is that the default icon was shown instead of a custom one, your visitors saw no errors :-)
This is the easiest to do and it will show your icon no matter what page your visitor adds to their favorites. Simply upload your new icon to the main directory of your site, ie. www.example.com/favicon.ico.
Thank You

404 error after checking browser cloudflare redirect url only

Hello i have 404 error every time there is a browser check and gives an address like “https://www.mywebsite.com/?cf_chl_managed_tk=pmd_lJ44g7MrHYK29BtRBtcFUNNs3Dzo_LT21.viOSdeYXY-1631907472-0-gqNtZGzNAqWjcnBszRzR” no problem if the browser is not checked.
This is done on all pages !
I use WordPress for information and the error is displayed in WordPress.
I use also Nginx.
Any help will be appreciated. Thank you
Edit: oddly in the admin it works the url "https://www.mywebsite.com/wp-admin/index.php?cf_chl_managed_tk=pmd_lJ44g7MrHYK29BtRBtcFUNNs3Dzo_LT21.viOSdeYXY-1631907472-0-gqNtZGzNAqWjcnBszRzR" is displayed then is redirected to the correct url "https://www.mywebsite.com/wp-admin/index.php"
If i desactive "Under attack Mode" all is work, but i absolutely have to keep it the site is always attacked!
Updating the plugin Hide My WP fixed the problem.

WordPress with ssl form let's encrypt, but homepage not fully secure. "Attackers might be able to see images.." message

Could you help me find out what to do with not fully secure message.
I have installed ssl certificate from let's encrypt, but my wordpress homepage has a message "Attackers might be able to see the images you're looking at on this site and trick you by modifying them".
The home page is still in development, with demo content. About what images chrome notification is telling? Something to do with cookies?
Thank you for your answers!
Edit: Does it have to do with the theme itself? Whole wordpress dashboard and login is served over proper secure ssl.
Sending images via http protocol is what triggers this issue. Using any content from a cdn that does not use https will also trigger this issue. This quote explains it pretty simply (the yellow padlock / warning of unencrypted content/images):
If a yellow padlock appears with a mini yield sign, the likely cause
is links in your site still refer to an unsecured page. Make sure that
all your images, menu items and links use https in the URL.
source
I would use a tool to help identify all non-encrypted file transports. One such tool would be something like Why No Padlock.
Did you enable https after installing WordPress? If so, you must change the WordPress address and Site Address under "General Settings" in WordPress. Make sure both addresses use https.
If your WordPress site address is set to use http, your server will force https but WordPress will serve certain images, like the favicon, over http. This triggers a "mixed content" warning.
I too had run into this issue. It appears there are many http: that need to be replaced with https:
You typically do this using a plugin called Better Search and Replace. Make sure you are adding colon (:) at the end of both http and https.
I found a working answer here
To check for issues on the chrome/opera inspection console (ctrl+shift+C) is also a great idea: I had setup all correctly and the issue was the footer image, not something you would check very often looking for this fix. I had applied SSL to many websites, sometimes the issue is just one simple link and this method helps find it.
I had the same problem where the home or index page was saying the page was not fully secure "Attackers might be able to see images blah blah blah"
After enabling https in general settings under site address and wordpress address I was still getting the insecure image warning on the index or home page.
The next step was to find out what images were not using the https ref on the index or home page.
In my case I viewed the page source of the page, by right mouse clicking the page in the chrome browser & looking for images url ref which were still showing http. I was using a sliding header and those images were showing http. So all I did was go into slider header in the appearance menu of the wordpress, and re-assign each of the header slider image for each frame. RE-checked the home page now the image urls were showing https. Bingo the secure lock symbol returned.
Obviously these image urls don't get updated via the general settings... which seems an oversight by whoever wrote the part of the word-press script.

Wordpress - Page renders fine, Web Sniffer returning HTTP Response Header 404

I hope someone can help, I've been going round and round in circles. I've tried calling my host 1and1 they basically told me it's nothing to do with them.
All my Wordpress pages render fine to the eye of the user.
However if I use http://web-sniffer.net and put any page other than the homepage it returns a 404 status.
The .htaccess file is the standard Wordpress one. I don't have any caching plugins installed.
Could anyone tell me how I fix this? Or what on earth is going on? I've been at this for hours reading tonnes of posts to no avail.
I am using a dedicated 1and1 server, within the settings in Plesk the IPv6 address was set to none. As soon as I added a IPv6 address it all worked!
Note I had another issue that Facebook wasn't able to scrape my URLs, this also fixed that. Wordpress - Shared link 404 on Facebook

WordPress home page not appearing

I have just installed a WordPress site on GoDaddy but unfortunately the home page of the site does not appear - just stays in waiting mode with the progress wheel spinning.
But if I go down a level to http://example.com/about-us, the site appears as required but going back to just http://example.com/ does not show anything?
Perhaps the home page is set to look up data from a location that is unavailable? Try looking up the source of the home page and see if it is trying to resolve a non-existent page. In addition you might like to use the W3C Validatior to check for errors before proceeding. You error otherwise seems quite vague.

Resources