Michael,

> 1. How does Warp know which interface, port, and IP address the connection
> comes in on? The port is specified by the user, so there's no purpose in
> Warp providing that to the application. The interface is (mostly) user
> specified as well. But it's not a request-specific piece of information
> anyway. If you wanted that information, why should it be part of the
> Request value? Warp could just provide it separately via a separate run
> function, e.g.:

I guess they want to know peer's port number. I don't know why it is
important.

However, I think that peer's IP address is important. If an
application can obtain combination of peer's IP address and HTTP
header, the application can tell whether or not communication is
encrypted.

--Kazu