on master help sign in
Update some Request fields
commitf71fa945e6bc7850081a1f0afe371fc0062f48b6 authorMichael Snoyman <michael@snoyman.com> dateMon 19 Aug 2013, 10:48 (13 years ago) parentfe2032a
1 file changed+6−13
wai/Network/Wai.hs+6−13
wai/Network/Wai.hs+6−13
@@ -80,22 +80,15 @@ data Request = Request
8080 -- /will/ include the leading question mark.
8181 -- Do not modify this raw value- modify queryString instead.
8282 , rawQueryString :: B.ByteString
83− -- | Generally the host requested by the user via the Host request header.
84− -- Backends are free to provide alternative values as necessary. This value
85− -- should not be used to construct URLs.
86− , serverName :: B.ByteString
87− -- | The listening port that the server received this request on. It is
88− -- possible for a server to listen on a non-numeric port (i.e., Unix named
89− -- socket), in which case this value will be arbitrary. Like 'serverName',
90− -- this value should not be used in URL construction.
91− , serverPort :: Int
9283 , requestHeaders :: H.RequestHeaders
9384 -- | Was this request made over an SSL connection?
9485 --
95− -- This value should /not/ be used, and will be removed in future revisions
96− -- of WAI. There is no meaningful way that a backend can indicate whether the
97− -- request is actually over a secure channel, due to issues of reverse
98− -- proxying.
86+ -- Note that this value will /not/ tell you if the client originally made
87+ -- this request over SSL, but rather whether the current connection is SSL.
88+ -- The distinction lies with reverse proxies. In many cases, the client will
89+ -- connect to a load balancer over SSL, but connect to the WAI handler
90+ -- without SSL. In such a case, @isSecure@ will be @False@, but from a user
91+ -- perspective, there is a secure connection.
9992 , isSecure :: Bool
10093 -- | The client\'s host information.
10194 , remoteHost :: SockAddr