> > >> For example, it HAS been published elsewhere that YouTube uses lighttpd, > > >> not Apache: <http://trac.lighttpd.net/trac/wiki/PoweredByLighttpd>. > > > > > > How do you explain these, then: > > > > > > http://www.youtube.com/results.xxx > > > http://www.youtube.com/results.php > > > http://www.youtube.com/results.py > > > > Server signature is usually configurable. > > Yeah, but I don't know why it's configured it that way. A good example > of a question that looks perfectly appropriate for YouTube's OSCON > session.
Actually, the fact that http://www.youtube.com/results.php returns legitimate content might be explainable by the fact that youtube was started as a PHP app so they might provide this URL for backward compatibility although today there is no PHP at all. See the abstract of Mike Solomon's OSCON talk: "YouTube began as a small PHP application. [...]" http://conferences.oreillynet.com/cs/os2007/view/e_sess/13435 -- http://mail.python.org/mailman/listinfo/python-list