Welcome to WebmasterWorld Guest from 188.8.131.52
Am I in good shape? (not to worry?)
One of those pages, provides 50% of all my traffic. Of course, that page is the one I would most like to see as https.
"How do I implement your ads on my SSL web pages?
We do provide SSL compliant ads. As this is a custom implementation, please mail us at email@example.com, and your Account Manager will generate the ad codes for your site."
"Ads targeted to individual pages."I WISH. Not for me, not yet. STILL by email request, only. All my pages have numerous, varied subject matter. Typically, they take the ad targeting from another popular page, and apply it to a page with a different subject. For me, this does NOT work, because it is NOT targeted to the page.
There may have been another issue, as well.As you found out, HTTPS pages with secure content errors (unsecure ads blocked) will not be indexed (since they are not secure) until fixed, so those pages will take extra time.
Mediadotnet ad code MUST BE CHANGED for https...I was slow to do this.
What is the status of this https issue with Google? will non https sites suffer a penalty?
I don't think I will ever understand caching.
My host fixed it in a few hours. Apparently, it is a little tricky on nginx.
But it is working now. No longer implemented in htaccess, but elsewhere in the maze.
I cannot "Leverage Browser Caching".As with “error” messages in GSC, sometimes you just have to put your fingers in your ears and hum loudly.
My score for everything is 100% - 98%. Always dinged 2% because I don't "Leverage Browser Caching".
I have always had an htaccess file.
If you are using an htaccess file in NGINX... Stop. It’s horrible for performance.At the risk of horribly (as it were) derailing this thread... If nginx doesn't use htaccess, how or why would the server even look for the file, let alone read it? Even apache doesn't recognize htaccess unless the server config file specifically says it can.
It can't be THAT big a hit, with just one line of code, can it?Extrapolating from htaccess within Apache: The issue is probably not so much the filesize itself, or the number of directives it contains, as its bare existence--or even the possibility of existence. On every request, the server first has to go looking for htaccess in every directory along the path.
the nginx web server is a reverse proxy that directly handles all static file requests, and forwards everything else to Apache, which would still be able to abide by the rules of any htaccess files.Does “static file” here mean “files that physically exist”? In an Apache-plus-nginx combo, who handles requests for nonexistent files, including vanilla 404s? Do they get dumped on Apache, which would explain the need for an ErrorDocument directive? And, contrariwise, if the requested file does exist, does the server still have to look for htaccess? Can you deny requests both on the nginx side and on the Apache side? So many questions ...