I know you're being facetious, but asking someone to learn a new language and then familiarise themselves with a project's whole codebase just to answer a simple question about privacy is not exactly helpful. Especially when the site is served by Apache, a whole separate program which keeps its own completely distinct logs, so the suggested course of action is not only a huge imposition but can't actually answer the question anyway.
As others have said, the answer is obvious from the behaviour of the site. But even if it were not, other aspects of the server's configuration would be highly relevant, indeed central to the matter, and the source code is unavailing.
You know, I specifically checked that before posting. Where I went wrong is that I didn't look at the HTML page itself; I looked at the images and CSS, which I erroneously assumed to be handled by the same program.
All images and CSS for this site are served by Apache but the actual text/html request is not. However - my point still stands, as the primary request is proxied by Apache and proxy requests, IIRC, are included, or can be configured to be included, in the Apache logs.
update: I am going to have to eat my words here. I have no evidence news.ycombinator.com is proxied by Apache. All the css and images are served by Apache, but they're hosted on a different domain and a different IP at ycombinator.com. I am kind of amazed PG wrote an HTTP server but .. apparently he did. Kudos.
As others have said, the answer is obvious from the behaviour of the site. But even if it were not, other aspects of the server's configuration would be highly relevant, indeed central to the matter, and the source code is unavailing.