The InCommon WAYF, which was taken out of service on 6 July 2011, is still receiving a relatively small number of requests. For example, during the week from June 30 to July 6, the legacy WAYF received the indicated number of requests from the following InCommon service providers:
31 https://expo.uw.edu/shibboleth 9 https://express.travel.ucla.edu/shibboleth/incommon 1 https://itarch-dev.stanford.edu/shibboleth/ 19 https://service1.internet2.edu/shibboleth 1 https://shib-db.grnoc.iu.edu/shibboleth 371 https://shib.lynda.com/shibboleth-sp 1 https://sp.tshhosting.com/shibboleth 7 https://spaces.ais.ucla.edu/incommon 4 https://uc.sumtotalsystems.com/shibboleth 11 https://ucsso.travelprefs.com 50 https://www.eqm.ucla.edu/shibboleth/incommon/sp 4 https://www.omnilert.net/shibboleth 25 https://www.webassign.net/Shibboleth 2 https://service1.internet2.edu/shibboleth 9 https://shibboleth.studentclearinghouse.org/shibboleth 217 https://ucsso.travelprefs.com
The URLs listed above are actually the entity IDs of each service provider. It's possible that these SPs are redirecting users to the legacy WAYF (which is a configuration issue), but it's much more likely that users are selecting bookmarks or clicking on links that still point to the legacy WAYF. This is indicated in the attached log file entries for these requests, some of which show an HTTP Referrer, which suggests the user may have clicked a link on a web page.