{"id":66376,"date":"2025-01-05T03:01:00","date_gmt":"2025-01-04T17:01:00","guid":{"rendered":"https:\/\/www.rjmprogramming.com.au\/ITblog\/?p=66376"},"modified":"2025-01-05T11:54:31","modified_gmt":"2025-01-05T01:54:31","slug":"almalinux-apache-status-report-inspiration-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/almalinux-apache-status-report-inspiration-tutorial\/","title":{"rendered":"AlmaLinux Apache Status Report Inspiration Tutorial"},"content":{"rendered":"
\"AlmaLinux<\/a>

AlmaLinux Apache Status Report Inspiration Tutorial<\/p><\/div>\n

Examining the RJM Programming’s Apache<\/a> web server’s cPanel<\/a>‘s …<\/p>\n


\nApache Status
\n<\/code><\/p>\n

… report, showing RJM Programming URL accesses in real time, can be very eye opening. Among recent surprises we got there were accesses ( regarding PHP $_SERVER[‘REQUEST_URI’] … ie. the stuff after www.rjmprogramming.com.au<\/i> ) starting with …<\/p>\n\n\n\n\n\n\n
Starting
with …<\/th>\n		… then.<\/font><\/th>\nOur initial response …<\/font><\/th>\nThe action we took …<\/th>\n<\/tr>\n
\/wiki\/<\/td>\nSai_Baba_of_Shirdi<\/a><\/font><\/td>\nWhat the …? Who are those guys?<\/a><\/font><\/td>\nRedirected to English
relevant Wikipedia<\/a> webpage …
404.shtml (in Apache
Document Root) change<\/font> …<\/td>\n

\n function onPageLoad() {
\n if (document.URL.indexOf('\/currency\/') != -1) {
\n location.href='\/\/www.rjmprogramming.com.au\/PHP\/country_currency_quiz.php#showcur=' + document.URL.split('\/currency\/')[1];
\n }<\/font>
\n if (document.URL.indexOf('\/wiki\/') != -1) {
\n location.href='\/\/wikipedia.org\/wiki\/' + document.URL.split('\/wiki\/')[1];
\n }<\/font>
\n \/\/ rest of code follows
\n }
\n<\/code><\/td>\n<\/tr>\n
\/currency\/<\/td>\nlbp-lebanese-pound<\/a><\/font><\/td>\nWe’re officially gobsmacked!<\/font><\/td>\n404.shtml (in Apache
Document Root) change<\/font> … then …
country_currency_quiz.php<\/a>
(with this live run<\/a> link),
featuring these changes<\/a><\/td>\n<\/tr>\n<\/table>\n

… that last one today’s work, borne out of Apache Status Fascination<\/i>!<\/p>\n

Making something out of nothing<\/i>?! We’ve got nothing to lose, and we may surprise some user out there (perhaps just mucking around)<\/font>.<\/p>\n

And so, with similar themes to HTML5 Time Tag Timeline AlmaLinux Debug Tutorial<\/a> we set out to make something out of nothing<\/i> here, and we’ve closely documented what we did regarding today’s animated GIF presentation<\/a>.<\/p>\n

\n

\n

Previous relevant HTML5 Time Tag Timeline AlmaLinux Debug Tutorial<\/a> is shown below.<\/p>\n

\"HTML5<\/a>

HTML5 Time Tag Timeline AlmaLinux Debug Tutorial<\/p><\/div>\n

Another day, another use for (in our case Google Chrome web browser) web inspector<\/i> functionality. Yes, even if the source of the issue is PHP (which we moved on from a CentOS starting with 5 version to an AlmaLinux version starting with an 8) we’re yet to see an issue that could not be resolved with the help of a clientside web inspector debugging arrangement. Of course, the simpler the PHP the more likely this is to happen, but we can’t emphasise enough how useful these web inspectors are.<\/p>\n

Today’s case in point revisits the use_time.htm clientside web application we talked about at HTML5 Time Tag Timeline Tutorial<\/a>. Moving to AlmaLinux, and revisiting it on trying …<\/p>\n

<\/img><\/p>\n

… as a reason we should add to the list<\/font> (of two we talked about at PHP Migration Software Strategies Tutorial<\/a>) …<\/p>\n

\n