http-reverse-proxy 0.4.4 → 0.4.5
raw patch · 3 files changed
+10/−4 lines, 3 filesPVP ok
version bump matches the API change (PVP)
API changes (from Hackage documentation)
+ Network.HTTP.ReverseProxy: instance GHC.Classes.Eq Network.HTTP.ReverseProxy.ProxyDest
+ Network.HTTP.ReverseProxy: instance GHC.Classes.Ord Network.HTTP.ReverseProxy.ProxyDest
+ Network.HTTP.ReverseProxy: instance GHC.Generics.Generic Network.HTTP.ReverseProxy.ProxyDest
+ Network.HTTP.ReverseProxy: instance GHC.Read.Read Network.HTTP.ReverseProxy.ProxyDest
+ Network.HTTP.ReverseProxy: instance GHC.Show.Show Network.HTTP.ReverseProxy.ProxyDest
Files
- ChangeLog.md +6/−2
- Network/HTTP/ReverseProxy.hs +3/−1
- http-reverse-proxy.cabal +1/−1
ChangeLog.md view
@@ -1,7 +1,11 @@+## 0.4.5++* add `Eq, Ord, Show, Read` instances to `ProxyDest`+ ## 0.4.4 -* add `rawTcpProxyTo` which can handle proxying connections without http headers - [#21](https://github.com/fpco/http-reverse-proxy/issues/21) +* add `rawTcpProxyTo` which can handle proxying connections without http headers+ [#21](https://github.com/fpco/http-reverse-proxy/issues/21) ## 0.4.3.3
Network/HTTP/ReverseProxy.hs view
@@ -1,3 +1,4 @@+{-# LANGUAGE DeriveGeneric #-} {-# LANGUAGE FlexibleContexts #-} {-# LANGUAGE MultiParamTypeClasses #-} {-# LANGUAGE OverloadedStrings #-}@@ -69,6 +70,7 @@ import qualified Data.Text as T import qualified Data.Text.Encoding as TE import Data.Word8 (isSpace, _colon, _cr)+import GHC.Generics (Generic) import Network.HTTP.Client (BodyReader, brRead) import qualified Network.HTTP.Client as HC import qualified Network.HTTP.Types as HT@@ -80,7 +82,7 @@ data ProxyDest = ProxyDest { pdHost :: !ByteString , pdPort :: !Int- }+ } deriving (Read, Show, Eq, Ord, Generic) -- | Set up a reverse proxy server, which will have a minimal overhead. --
http-reverse-proxy.cabal view
@@ -1,5 +1,5 @@ name: http-reverse-proxy-version: 0.4.4+version: 0.4.5 synopsis: Reverse proxy HTTP requests, either over raw sockets or with WAI description: Provides a simple means of reverse-proxying HTTP requests. The raw approach uses the same technique as leveraged by keter, whereas the WAI approach performs full request/response parsing via WAI and http-conduit. homepage: https://github.com/fpco/http-reverse-proxy