05-01-2019
Hey Jim,
Thanks for replying,
Google Webmaster Tools provide the URLS of all the 404 errors.
When I test them, the URLs are all OK.
When I run some Chome extension to read the HTTPD headers, I see 404s which become 200s. It is like our URL rewriting software is causing this, but when I ask DragonByte support, they tell me their software does not cause this problem and are not helpful.
The problem started when we moved to a new server and a new version of Apache, so my guess is the issue is in the Apache2 configuration, but I cannot find the problem.
It's been like this (going down and down in the search ranking and number of pages indexed) since I moved to the new data center last year.
I cannot figure it out.
Let me know if you need to be added to webmaster tools for access, if you are experienced in GWT.
Thanks.
7 More Discussions You Might Find Interesting
1. SCO
when I do a tape status /dev/rStp0 I get the following on a new tape and I have tried several:
Status : ready beginning-of-tape
soft errors : 0
hard errors: 2
underruns: 5
My BackupEdge has stopped backing up my system because it asks for a new volume yet my total system data is under 20... (5 Replies)
Discussion started by: psytropic
5 Replies
2. Shell Programming and Scripting
I am looking for some tips or suggestions in how to do the following.
1) From a Solaris server, I run the command iostat -En and receive output that is similiar to the following which shows your disks along with the cdrom/dvdrom:
c0t2d0 Soft Errors: 0 Hard Errors: 0 Transport... (1 Reply)
Discussion started by: sunsysadm2003
1 Replies
3. Solaris
hi friends,
How will you clear the soft error on disk ? (2 Replies)
Discussion started by: rajaramrnb
2 Replies
4. Solaris
Hi guys,
I had a solaris box, with veritas controled disk.
1 disc is showing soft errors, how can I repair the soft errors?
Please help.
Cheers; (4 Replies)
Discussion started by: Mujakol
4 Replies
5. Shell Programming and Scripting
I am trying to use wget to make a local copy of this website
accuscore.com/fantasy-sports/nfl-fantasy-sports/Current-Week-DEF-ST (i have the http:// in front, but the forum will not allow me to put it in at this time)
Whenever i try to use wget i receive an "Error 404: Not found". I tried the... (4 Replies)
Discussion started by: problemss
4 Replies
6. What is on Your Mind?
For the first time in the history of the site Google Search Console (GSC) has unix.com showing "no mobile viewability errors". This is no small achievement considering the hundreds of thousand of lines of legacy code we run at a site which has been around much longer than Facebook or LinkedIn:
... (0 Replies)
Discussion started by: Neo
0 Replies
7. What is on Your Mind?
Getting a bit more comfortable making quick YT videos in 4K, here is:
Search Engine Optimization | How To Fix Soft 404 Errors and A.I. Tales from Google Search Console
https://youtu.be/I6b9T2qcqFo (0 Replies)
Discussion started by: Neo
0 Replies
LEARN ABOUT MOJAVE
apache2::porting
install::TempContent::Objects::mod_perl-2.0.9::docs::apiUseraContribuinstall::TempContent::Objects::mod_perl-2.0.9::docs::api::Apache2::porting(3)
NAME
Apache2::porting -- a helper module for mod_perl 1.0 to mod_perl 2.0 porting
Synopsis
# either add at the very beginning of startup.pl
use Apache2::porting;
# or httpd.conf
PerlModule Apache2::porting
# now issue requests and look at the error_log file for hints
Description
"Apache2::porting" helps to port mod_perl 1.0 code to run under mod_perl 2.0. It doesn't provide any back-compatibility functionality,
however it knows to trap methods calls that are no longer in the mod_perl 2.0 API and tell what should be used instead if at all. If you
attempts to use mod_perl 2.0 methods without first loading the modules that contain them, it will tell you which modules you need to load.
Finally if your code tries to load modules that no longer exist in mod_perl 2.0 it'll also tell you what are the modules that should be
used instead.
"Apache2::porting" communicates with users via the error_log file. Everytime it traps a problem, it logs the solution (if it finds one) to
the error log file. If you use this module coupled with "Apache2::Reload" you will be able to port your applications quickly without
needing to restart the server on every modification.
It starts to work only when child process start and doesn't work for the code that gets loaded at the server startup. This limitation is
explained in the Culprits section.
It relies heavily on "ModPerl::MethodLookup". which can also be used manually to lookup things.
Culprits
"Apache2::porting" uses the "UNIVERSAL::AUTOLOAD" function to provide its functionality. However it seems to be impossible to create
"UNIVERSAL::AUTOLOAD" at the server startup, Apache segfaults on restart. Therefore it performs the setting of "UNIVERSAL::AUTOLOAD" only
during the child_init phase, when child processes start. As a result it can't help you with things that get preloaded at the server
startup.
If you know how to resolve this problem, please let us know. To reproduce the problem try to use an earlier phase, e.g.
"PerlPostConfigHandler":
Apache2::ServerUtil->server->push_handlers(PerlPostConfigHandler => &porting_autoload);
META: Though there is a better solution at work, which assigns AUTOLOAD for each class separately, instead of using UNIVERSAL. See the
discussion on the dev list (hint: search the archive for EazyLife)
See Also
mod_perl 2.0 documentation.
Copyright
mod_perl 2.0 and its core modules are copyrighted under The Apache Software License, Version 2.0.
Authors
The mod_perl development team and numerous contributors.
perl v5.18.2 2install::TempContent::Objects::mod_perl-2.0.9::docs::api::Apache2::porting(3)