On 2 February 2011, a redirect from the InCommon WAYF to the InCommon Discovery Service was put in place and the WAYF was scheduled for complete removal on 6 July 2011. In the interim, service providers throughout the Federation adjusted their software configurations to point at the Discovery Service, not the WAYF.
As of 7 July 2011, the InCommon WAYF 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 users trying to access 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/ 21 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 50 https://www.eqm.ucla.edu/shibboleth/incommon/sp 4 https://www.omnilert.net/shibboleth 25 https://www.webassign.net/Shibboleth 9 https://shibboleth.studentclearinghouse.org/shibboleth 228 https://ucsso.travelprefs.com
The URLs listed above are actually the entity IDs of each service provider. It's possible that these SPs are still 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 mistakenly 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.