×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hey Justin,
This is just a guess based on my understanding of how Apache does HTTP basic auth, but there's a chance the browser isn't sending the auth details with the first request, and when the browser sends back the 401 (Indicating it needs authorization) the browser is re-submitting the request with the auth details included. This seems to match up with the response and rejected counts being extremely close in count.
If you aren't noticing anything acting odd when accessing the server through your browser, it's probably not anything to worry about.
- Steven
-----Original Message-----
From: WEB400 <web400-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Justin Taylor
Sent: Tuesday, August 13, 2019 11:10 AM
To: WEB400 (web400@xxxxxxxxxxxxxxxxxx) <web400@xxxxxxxxxxxxxxxxxx>
Subject: [WEB400] Requests rejected
I have an Apache server that in IBM Web Admin for i, under Real Time Server Statistics shows:
Requests: 4269
Response: 2143
Requests rejected: 2126
Should I be concerned about all the rejects? In the access_log, virtually every request shows a 401 followed immediately by a 200. The 401s don't show a user, but the 200s do. The server is HTTPS, if that matters.
TIA
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list To post a message email: WEB400@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx Before posting, please take a moment to review the archives at
https://archive.midrange.com/web400.
midrange.com
