NuGet Gallery Feed for OcelotOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2024-03-04T12:22:44Zhttps://api.nuget.org/v3-flatcontainer/ocelot/23.1.0/iconhttps://www.nuget.org/packages/Ocelot/23.1.0Ocelot 23.1.02024-03-04T12:19:39Z2024-03-04T12:22:44Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/23.0.0Ocelot 23.0.02024-02-13T14:13:36Z2024-02-13T14:16:36Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/22.0.1Ocelot 22.0.12023-12-08T09:20:32Z2023-12-08T09:23:03Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/22.0.0Ocelot 22.0.02023-11-28T08:18:01Z2023-11-28T08:20:34Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/21.0.0Ocelot 21.0.02023-11-21T07:53:10Z2023-11-21T07:55:30Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/20.0.0Ocelot 20.0.02023-10-07T08:15:14Z2023-10-07T08:17:15Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/19.0.4Ocelot 19.0.42023-10-06T11:15:46Z2023-10-06T11:17:48Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/19.0.3Ocelot 19.0.32023-09-21T06:55:32Z2023-09-21T06:57:34Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/19.0.2Ocelot 19.0.22023-04-22T22:16:13Z2023-04-22T22:18:13Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/19.0.1Ocelot 19.0.12023-04-22T21:10:55Z2023-04-22T21:13:27Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/19.0.0Ocelot 19.0.02023-04-22T20:57:21Z2023-04-22T21:00:22Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/18.0.0Ocelot 18.0.02022-01-20T20:45:49Z2022-01-20T20:47:54Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/17.0.1Ocelot 17.0.12021-12-20T22:14:03Z2021-12-20T22:16:05Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/17.0.0Ocelot 17.0.02020-12-11T10:27:54Z2020-12-11T10:30:29Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/16.0.2Ocelot 16.0.22020-12-11T09:57:51Z2020-12-11T10:00:22Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/16.0.1Ocelot 16.0.12020-05-25T17:54:06Z2020-05-25T17:56:08Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/16.0.0Ocelot 16.0.02020-05-23T19:56:33Z2020-05-23T19:58:35Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/15.0.7Ocelot 15.0.72020-05-23T14:54:07Z2020-05-23T14:56:08Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/15.0.6Ocelot 15.0.62020-04-13T17:47:48Z2020-04-13T17:49:48Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/15.0.5Ocelot 15.0.52020-04-13T17:42:05Z2020-04-13T17:44:37Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/15.0.4Ocelot 15.0.42020-04-13T15:52:47Z2020-04-13T15:55:21Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/15.0.3Ocelot 15.0.32020-04-13T11:50:39Z2020-04-13T11:53:08Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/15.0.2Ocelot 15.0.22020-04-12T18:30:18Z2020-04-12T18:32:18Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/15.0.1Ocelot 15.0.12020-04-11T18:50:34Z2020-04-11T18:52:36Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/15.0.0Ocelot 15.0.02020-04-11T10:52:50Z2020-04-11T10:54:53Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/14.1.3Ocelot 14.1.32020-04-11T10:14:15Z2020-04-11T10:16:17Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/14.1.2Ocelot 14.1.22020-04-11T09:04:07Z2020-04-11T09:07:02Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/14.1.1Ocelot 14.1.12020-04-11T08:56:53Z2020-04-11T08:58:55Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/14.1.0Ocelot 14.1.02020-03-13T09:19:54Z2020-03-13T09:21:54Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/14.0.12Ocelot 14.0.122020-03-11T20:32:56Z2020-03-11T20:34:55Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/14.0.11Ocelot 14.0.112020-02-22T12:33:40Z2020-02-22T12:35:41Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/14.0.10Ocelot 14.0.102020-02-21T16:57:06Z2020-02-21T16:59:20Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/14.0.9Ocelot 14.0.92020-02-09T18:18:44Z2020-02-09T18:20:46Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/14.0.8Ocelot 14.0.82020-02-09T18:13:34Z2020-02-09T18:15:37Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/14.0.7Ocelot 14.0.72020-02-09T17:00:05Z2020-02-09T17:02:05Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/14.0.6Ocelot 14.0.62020-02-09T14:08:09Z2020-02-09T14:10:11Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/14.0.5Ocelot 14.0.52020-02-04T20:57:35Z2020-02-04T20:59:37Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/14.0.4Ocelot 14.0.42020-02-04T20:12:48Z2020-02-04T20:14:50Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/14.0.3Ocelot 14.0.32020-01-19T17:50:50Z2020-01-19T17:52:52Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/14.0.2Ocelot 14.0.22020-01-19T15:53:43Z2020-01-19T15:55:46Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/14.0.1Ocelot 14.0.12020-01-19T15:42:29Z2020-01-19T15:44:31Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/14.0.0Ocelot 14.0.02020-01-19T15:33:11Z2020-01-19T15:35:43Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.9.0-alpha0115Ocelot 13.9.0-alpha01152019-11-05T16:43:25Z2019-11-05T16:50:30Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.8.5Ocelot 13.8.52020-01-18T22:23:44Z2020-01-18T22:25:47Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.8.4Ocelot 13.8.42020-01-18T14:56:03Z2020-01-18T14:59:05Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.8.3Ocelot 13.8.32020-01-18T14:39:32Z2020-01-18T14:41:33Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.8.2Ocelot 13.8.22020-01-17T22:16:59Z2020-01-17T22:18:32Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.8.1Ocelot 13.8.12020-01-17T07:57:10Z2020-01-17T07:59:41Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.8.0Ocelot 13.8.02019-10-28T07:42:58Z2019-10-28T08:05:56Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.8.0-alpha0022Ocelot 13.8.0-alpha00222019-10-28T07:28:44Z2019-10-28T07:30:47Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.8.0-alpha0019Ocelot 13.8.0-alpha00192019-09-23T15:35:36Z2019-09-23T15:37:08Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.8.0-alpha0018Ocelot 13.8.0-alpha00182019-09-12T15:17:21Z2019-09-12T15:21:33Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.8.0-alpha0017Ocelot 13.8.0-alpha00172019-09-12T15:12:13Z2019-09-12T15:17:26Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.8.0-alpha0016Ocelot 13.8.0-alpha00162019-08-23T16:00:03Z2019-08-23T16:04:16Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.8.0-alpha0015Ocelot 13.8.0-alpha00152019-08-23T15:55:09Z2019-08-23T15:59:19Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.8.0-alpha0014Ocelot 13.8.0-alpha00142019-08-12T17:11:32Z2019-08-12T17:16:43Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.8.0-alpha0010Ocelot 13.8.0-alpha00102019-07-28T15:36:52Z2019-07-28T15:41:03Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.8.0-alpha0008Ocelot 13.8.0-alpha00082019-07-28T13:35:57Z2019-07-28T13:40:09Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.8.0-alpha0006Ocelot 13.8.0-alpha00062019-07-01T11:29:02Z2019-07-01T11:33:13Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.8.0-alpha0005Ocelot 13.8.0-alpha00052019-07-01T05:23:52Z2019-07-01T05:28:02Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.8.0-alpha0004Ocelot 13.8.0-alpha00042019-07-01T02:11:24Z2019-07-01T02:15:33Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.8.0-alpha0003Ocelot 13.8.0-alpha00032019-06-25T03:13:15Z2019-06-25T03:17:26Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.8.0-alpha0002Ocelot 13.8.0-alpha00022019-06-18T06:41:50Z2019-06-18T06:45:55Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.7.0-alpha0011Ocelot 13.7.0-alpha00112019-06-01T11:27:07Z2019-06-01T11:31:15Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.7.0-alpha0010Ocelot 13.7.0-alpha00102019-05-30T15:03:30Z2019-05-30T15:09:00Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.7.0-alpha0009Ocelot 13.7.0-alpha00092019-05-30T07:06:39Z2019-05-30T07:10:49Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.7.0-alpha0008Ocelot 13.7.0-alpha00082019-05-30T07:01:07Z2019-05-30T07:05:16Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.7.0-alpha0007Ocelot 13.7.0-alpha00072019-05-28T03:05:24Z2019-05-28T03:09:35Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.7.0-alpha0006Ocelot 13.7.0-alpha00062019-05-27T08:28:21Z2019-05-27T08:32:29Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.7.0-alpha0005Ocelot 13.7.0-alpha00052019-05-24T02:11:00Z2019-05-24T02:15:07Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.7.0-alpha0004Ocelot 13.7.0-alpha00042019-05-23T01:43:46Z2019-05-23T01:47:55Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.7.0-alpha0003Ocelot 13.7.0-alpha00032019-05-22T13:09:32Z2019-05-22T13:13:44Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.7.0-alpha0002Ocelot 13.7.0-alpha00022019-05-22T01:53:12Z2019-05-22T01:57:18Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.6.0-alpha0014Ocelot 13.6.0-alpha00142019-05-20T07:52:52Z2019-05-20T07:57:01Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.6.0-alpha0012Ocelot 13.6.0-alpha00122019-05-13T05:09:31Z2019-05-13T05:13:42Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.6.0-alpha0011Ocelot 13.6.0-alpha00112019-05-13T05:04:27Z2019-05-13T05:09:36Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.6.0-alpha0010Ocelot 13.6.0-alpha00102019-05-10T03:40:44Z2019-05-10T03:44:53Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.6.0-alpha0008Ocelot 13.6.0-alpha00082019-05-07T02:59:52Z2019-05-07T03:04:01Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.6.0-alpha0007Ocelot 13.6.0-alpha00072019-05-04T06:37:13Z2019-05-04T06:41:24Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.6.0-alpha0006Ocelot 13.6.0-alpha00062019-05-04T06:32:45Z2019-05-04T06:36:53Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.6.0-alpha0004Ocelot 13.6.0-alpha00042019-04-13T18:18:31Z2019-04-13T18:22:44Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.6.0-alpha0002Ocelot 13.6.0-alpha00022019-04-13T18:13:37Z2019-04-13T18:17:47Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.6.0-alpha0001Ocelot 13.6.0-alpha00012019-04-08T02:57:06Z2019-04-08T03:01:14Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.5.2Ocelot 13.5.22019-06-01T12:09:32Z2019-06-01T12:15:21Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.5.1Ocelot 13.5.12019-05-20T08:33:36Z2019-05-20T08:37:45Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.5.0Ocelot 13.5.02019-03-30T13:01:38Z2019-03-30T13:05:50Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.5.0-alpha0056Ocelot 13.5.0-alpha00562019-03-30T09:26:17Z2019-03-30T09:31:28Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.5.0-alpha0055Ocelot 13.5.0-alpha00552019-03-29T19:30:11Z2019-03-29T19:34:26Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.5.0-alpha0054Ocelot 13.5.0-alpha00542019-03-29T19:16:28Z2019-03-29T19:20:39Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.5.0-alpha0053Ocelot 13.5.0-alpha00532019-03-24T11:03:15Z2019-03-24T11:07:26Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.5.0-alpha0001Ocelot 13.5.0-alpha00012019-03-23T21:39:04Z2019-03-23T21:43:15Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.4.1Ocelot 13.4.12019-03-23T21:46:53Z2019-03-23T21:51:02Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.4.0-alpha0001Ocelot 13.4.0-alpha00012019-03-23T21:16:23Z2019-03-23T21:20:36Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.3.0-alpha0001Ocelot 13.3.0-alpha00012019-03-23T20:58:31Z2019-03-23T21:02:44Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.2.0-alpha0034Ocelot 13.2.0-alpha00342019-03-22T22:35:01Z2019-03-22T22:39:09Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.2.0-alpha0033Ocelot 13.2.0-alpha00332019-03-22T12:46:20Z2019-03-22T12:50:36Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.2.0-alpha0031Ocelot 13.2.0-alpha00312019-03-22T12:29:28Z2019-03-22T12:37:42Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.2.0-alpha0030Ocelot 13.2.0-alpha00302019-03-19T22:36:25Z2019-03-19T22:40:38Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.2.0-alpha0026Ocelot 13.2.0-alpha00262019-03-19T14:43:25Z2019-03-19T14:47:32Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.2.0-alpha0024Ocelot 13.2.0-alpha00242019-03-12T23:12:25Z2019-03-12T23:16:31Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.2.0-alpha0023Ocelot 13.2.0-alpha00232019-03-12T02:37:42Z2019-03-12T02:41:52Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.2.0-alpha0022Ocelot 13.2.0-alpha00222019-03-11T14:44:50Z2019-03-11T14:49:01Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.2.0-alpha0021Ocelot 13.2.0-alpha00212019-03-11T14:06:07Z2019-03-11T14:10:20Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.2.0-alpha0020Ocelot 13.2.0-alpha00202019-03-11T14:00:13Z2019-03-11T14:04:22Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.2.0-alpha0015Ocelot 13.2.0-alpha00152019-02-25T20:14:19Z2019-02-25T20:18:29Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.2.0-alpha0010Ocelot 13.2.0-alpha00102019-01-31T10:26:25Z2019-01-31T10:30:39Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.2.0-alpha0009Ocelot 13.2.0-alpha00092019-01-27T16:25:37Z2019-01-27T16:29:44Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.2.0-alpha0008Ocelot 13.2.0-alpha00082019-01-27T16:21:25Z2019-01-27T16:25:38Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.2.0-alpha0007Ocelot 13.2.0-alpha00072019-01-27T11:48:11Z2019-01-27T11:52:24Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.2.0-alpha0006Ocelot 13.2.0-alpha00062019-01-26T15:21:02Z2019-01-26T15:25:37Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.2.0-alpha0004Ocelot 13.2.0-alpha00042019-01-26T15:16:26Z2019-01-26T15:21:01Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.2.0-alpha0003Ocelot 13.2.0-alpha00032019-01-18T20:43:12Z2019-01-18T20:47:22Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.2.0-alpha0001Ocelot 13.2.0-alpha00012019-01-16T13:02:23Z2019-01-16T13:06:34Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.1.0-alpha0003Ocelot 13.1.0-alpha00032019-01-11T21:01:09Z2019-01-11T21:05:20Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.1.0-alpha0002Ocelot 13.1.0-alpha00022019-01-11T14:01:18Z2019-01-11T14:05:29Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.1.0-alpha0001Ocelot 13.1.0-alpha00012019-01-11T09:04:57Z2019-01-11T09:09:10Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.0.0Ocelot 13.0.02019-01-13T12:38:28Z2019-01-13T12:42:34Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/13.0.0-alpha0028Ocelot 13.0.0-alpha00282019-01-07T20:02:14Z2019-01-07T20:06:28Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/12.1.0-unstable0009Ocelot 12.1.0-unstable00092018-09-30T09:21:17Z2018-09-30T09:25:29Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/12.1.0-unstable0007Ocelot 12.1.0-unstable00072018-09-25T20:06:19Z2018-09-25T20:10:26Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/12.1.0-unstable0005Ocelot 12.1.0-unstable00052018-09-25T19:34:02Z2018-09-25T19:38:10Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/12.1.0-unstable0004Ocelot 12.1.0-unstable00042018-09-25T17:35:46Z2018-09-25T17:39:52Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/12.1.0-unstable0003Ocelot 12.1.0-unstable00032018-09-24T07:26:38Z2018-09-24T07:30:50Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/12.1.0-unstable0002Ocelot 12.1.0-unstable00022018-09-24T06:59:25Z2018-09-24T07:03:39Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/12.1.0-unstable0001Ocelot 12.1.0-unstable00012018-09-22T07:54:47Z2018-09-22T07:59:00Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/12.1.0-alpha0027Ocelot 12.1.0-alpha00272019-01-03T13:58:58Z2019-01-03T14:03:14Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/12.1.0-alpha0026Ocelot 12.1.0-alpha00262018-12-26T20:12:47Z2018-12-26T20:16:56Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/12.1.0-alpha0025Ocelot 12.1.0-alpha00252018-12-26T16:36:12Z2018-12-26T16:40:40Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/12.1.0-alpha0024Ocelot 12.1.0-alpha00242018-12-17T19:57:18Z2018-12-17T20:01:32Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/12.1.0-alpha0020Ocelot 12.1.0-alpha00202018-12-17T19:38:48Z2018-12-17T19:43:01Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/12.1.0-alpha0019Ocelot 12.1.0-alpha00192018-12-16T15:03:07Z2018-12-16T15:07:22Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/12.1.0-alpha0015Ocelot 12.1.0-alpha00152018-12-16T14:58:13Z2018-12-16T15:02:25Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/12.1.0-alpha0014Ocelot 12.1.0-alpha00142018-12-08T07:45:22Z2018-12-08T07:49:31Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/12.1.0-alpha0013Ocelot 12.1.0-alpha00132018-10-13T16:55:40Z2018-10-13T16:59:55Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/12.1.0-alpha0011Ocelot 12.1.0-alpha00112018-10-13T16:51:31Z2018-10-13T16:55:43Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/12.1.0-alpha0010Ocelot 12.1.0-alpha00102018-10-13T10:58:05Z2018-10-13T11:02:14Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/12.0.1Ocelot 12.0.12018-09-30T09:17:09Z2018-09-30T09:21:20Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/12.0.0Ocelot 12.0.02018-09-20T17:53:29Z2018-09-20T17:57:43Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/12.0.0-unstable0014Ocelot 12.0.0-unstable00142018-09-20T17:38:02Z2018-09-20T17:42:16Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/11.1.0-unstable0009Ocelot 11.1.0-unstable00092018-09-20T15:59:18Z2018-09-20T16:03:26Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/11.1.0-unstable0008Ocelot 11.1.0-unstable00082018-09-12T18:54:25Z2018-09-12T18:58:40Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/11.1.0-unstable0007Ocelot 11.1.0-unstable00072018-09-12T06:47:46Z2018-09-12T06:51:57Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/11.1.0-unstable0006Ocelot 11.1.0-unstable00062018-09-12T06:38:07Z2018-09-12T06:42:13Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/11.1.0-unstable0005Ocelot 11.1.0-unstable00052018-09-11T20:49:48Z2018-09-11T20:54:00Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/11.1.0-unstable0003Ocelot 11.1.0-unstable00032018-09-04T21:32:22Z2018-09-04T22:44:08Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/11.1.0-unstable0002Ocelot 11.1.0-unstable00022018-09-03T20:36:09Z2018-09-03T20:40:21Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/11.1.0-unstable0001Ocelot 11.1.0-unstable00012018-09-03T07:01:56Z2018-09-03T07:06:07Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/11.0.3Ocelot 11.0.32018-09-13T17:43:30Z2018-09-13T17:47:44Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/11.0.2Ocelot 11.0.22018-09-03T20:52:27Z2018-09-03T20:56:41Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/11.0.1Ocelot 11.0.12018-09-03T17:24:19Z2018-09-03T17:28:33Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/11.0.0Ocelot 11.0.02018-09-01T12:25:18Z2018-09-01T12:29:31Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/11.0.0-unstable0021Ocelot 11.0.0-unstable00212018-09-01T12:14:25Z2018-09-01T12:18:42Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/11.0.0-unstable0020Ocelot 11.0.0-unstable00202018-08-31T17:38:23Z2018-08-31T17:42:38Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/10.1.0-unstable0019Ocelot 10.1.0-unstable00192018-08-31T17:32:41Z2018-08-31T17:36:52Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/10.1.0-unstable0018Ocelot 10.1.0-unstable00182018-08-30T05:57:48Z2018-08-30T06:01:57Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/10.1.0-unstable0017Ocelot 10.1.0-unstable00172018-08-28T18:01:02Z2018-08-28T18:05:10Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/10.1.0-unstable0016Ocelot 10.1.0-unstable00162018-08-27T16:51:35Z2018-08-27T16:55:47Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/10.1.0-unstable0015Ocelot 10.1.0-unstable00152018-08-26T11:42:19Z2018-08-26T11:46:29Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/10.1.0-unstable0013Ocelot 10.1.0-unstable00132018-08-25T11:39:44Z2018-08-25T11:43:55Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/10.1.0-unstable0012Ocelot 10.1.0-unstable00122018-08-25T11:36:27Z2018-08-25T11:40:37Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/10.1.0-unstable0011Ocelot 10.1.0-unstable00112018-08-20T21:32:31Z2018-08-20T21:36:43Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/10.1.0-unstable0010Ocelot 10.1.0-unstable00102018-08-19T13:01:50Z2018-08-19T13:07:03Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/10.1.0-unstable0009Ocelot 10.1.0-unstable00092018-08-19T12:00:54Z2018-08-19T12:06:07Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/10.1.0-unstable0008Ocelot 10.1.0-unstable00082018-08-19T09:17:25Z2018-08-19T09:22:33Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/10.1.0-unstable0007Ocelot 10.1.0-unstable00072018-08-14T19:54:18Z2018-08-14T19:59:28Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/10.1.0-unstable0006Ocelot 10.1.0-unstable00062018-08-14T17:43:36Z2018-08-14T17:48:50Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/10.1.0-unstable0005Ocelot 10.1.0-unstable00052018-08-14T17:28:56Z2018-08-14T17:34:03Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/10.1.0-unstable0004Ocelot 10.1.0-unstable00042018-08-14T07:22:30Z2018-08-14T07:27:42Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/10.1.0-unstable0003Ocelot 10.1.0-unstable00032018-08-12T19:32:17Z2018-08-12T19:37:34Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/10.1.0-unstable0002Ocelot 10.1.0-unstable00022018-08-12T17:24:26Z2018-08-12T17:29:38Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/10.1.0-unstable0001Ocelot 10.1.0-unstable00012018-08-12T16:50:28Z2018-08-12T16:55:35Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/10.0.4Ocelot 10.0.42018-08-25T12:24:33Z2018-08-25T12:28:47Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/10.0.3Ocelot 10.0.32018-08-19T12:20:48Z2018-08-19T12:25:58Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/10.0.2Ocelot 10.0.22018-08-14T20:05:23Z2018-08-14T20:10:35Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/10.0.1Ocelot 10.0.12018-08-12T19:43:07Z2018-08-12T19:48:16Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/10.0.0Ocelot 10.0.02018-08-12T14:49:52Z2018-08-12T14:54:59Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/9.1.0-unstable0001Ocelot 9.1.0-unstable00012018-08-12T14:17:32Z2018-08-12T14:22:43Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/9.0.0Ocelot 9.0.02018-08-12T12:37:42Z2018-08-12T12:42:49Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/9.0.0-unstable0041Ocelot 9.0.0-unstable00412018-08-12T12:12:57Z2018-08-12T12:18:10Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0040Ocelot 8.1.0-unstable00402018-08-12T09:20:38Z2018-08-12T09:26:13Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0039Ocelot 8.1.0-unstable00392018-08-11T17:48:56Z2018-08-11T17:54:05Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0037Ocelot 8.1.0-unstable00372018-08-11T12:54:40Z2018-08-11T12:59:52Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0036Ocelot 8.1.0-unstable00362018-08-11T10:57:12Z2018-08-11T11:02:22Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0035Ocelot 8.1.0-unstable00352018-08-04T14:21:19Z2018-12-15T06:15:25Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0034Ocelot 8.1.0-unstable00342018-08-04T07:26:24Z2018-12-15T06:15:25Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0031Ocelot 8.1.0-unstable00312018-08-04T07:21:11Z2018-12-15T06:15:24Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0030Ocelot 8.1.0-unstable00302018-08-04T07:05:52Z2018-12-15T06:15:28Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0029Ocelot 8.1.0-unstable00292018-08-03T07:19:55Z2018-12-15T06:15:25Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0028Ocelot 8.1.0-unstable00282018-08-02T19:46:40Z2018-12-15T06:15:25Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0027Ocelot 8.1.0-unstable00272018-08-02T17:37:49Z2018-12-15T06:15:30Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0026Ocelot 8.1.0-unstable00262018-08-01T22:57:39Z2018-12-15T06:15:25Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0025Ocelot 8.1.0-unstable00252018-07-31T20:35:38Z2018-12-15T06:16:45Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0023Ocelot 8.1.0-unstable00232018-07-31T20:28:45Z2018-12-15T06:16:45Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0022Ocelot 8.1.0-unstable00222018-07-31T18:25:19Z2018-12-15T06:16:45Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0021Ocelot 8.1.0-unstable00212018-07-31T17:42:39Z2018-12-15T06:16:45Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0020Ocelot 8.1.0-unstable00202018-07-30T22:18:52Z2018-12-15T06:16:45Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0019Ocelot 8.1.0-unstable00192018-07-30T21:48:02Z2018-12-15T06:16:45Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0018Ocelot 8.1.0-unstable00182018-07-30T06:53:22Z2018-12-15T06:16:45Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0017Ocelot 8.1.0-unstable00172018-07-30T06:10:54Z2018-12-15T06:16:45Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0016Ocelot 8.1.0-unstable00162018-07-29T19:36:27Z2018-12-15T06:16:52Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0015Ocelot 8.1.0-unstable00152018-07-29T17:27:15Z2018-12-15T06:16:50Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0014Ocelot 8.1.0-unstable00142018-07-27T22:17:40Z2018-12-15T06:16:54Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0013Ocelot 8.1.0-unstable00132018-07-27T17:05:10Z2018-12-15T06:16:46Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0012Ocelot 8.1.0-unstable00122018-07-25T07:50:06Z2018-12-15T06:16:52Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0011Ocelot 8.1.0-unstable00112018-07-25T07:39:04Z2018-12-15T06:16:50Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0010Ocelot 8.1.0-unstable00102018-07-23T17:21:28Z2018-12-15T06:16:45Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0009Ocelot 8.1.0-unstable00092018-07-21T10:27:32Z2018-12-15T06:16:52Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0008Ocelot 8.1.0-unstable00082018-07-21T08:05:25Z2018-12-15T06:16:52Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0006Ocelot 8.1.0-unstable00062018-07-20T22:15:15Z2018-12-15T06:16:52Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0005Ocelot 8.1.0-unstable00052018-07-20T21:44:32Z2018-12-15T06:16:53Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0004Ocelot 8.1.0-unstable00042018-07-20T21:37:12Z2018-12-15T06:17:52Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0003Ocelot 8.1.0-unstable00032018-07-19T16:56:19Z2018-12-15T06:16:54Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0002Ocelot 8.1.0-unstable00022018-07-19T16:51:31Z2018-12-15T06:16:53Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.1.0-unstable0001Ocelot 8.1.0-unstable00012018-07-12T18:33:20Z2018-12-15T06:16:55Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.0.8Ocelot 8.0.82018-08-11T14:21:42Z2018-08-11T14:26:49Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.0.7Ocelot 8.0.72018-08-04T08:01:41Z2018-12-15T06:16:55Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.0.6Ocelot 8.0.62018-08-03T09:50:47Z2018-12-15T06:16:52Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.0.5Ocelot 8.0.52018-08-03T06:53:26Z2018-12-15T06:16:57Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.0.4Ocelot 8.0.42018-07-30T06:49:21Z2018-12-15T06:16:50Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.0.3Ocelot 8.0.32018-07-28T07:21:54Z2018-12-15T06:16:55Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.0.2Ocelot 8.0.22018-07-25T07:51:01Z2018-12-15T06:16:57Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.0.1Ocelot 8.0.12018-07-21T08:29:35Z2018-12-15T06:16:57Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.0.0Ocelot 8.0.02018-07-11T05:56:09Z2018-12-15T06:16:57Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/8.0.0-unstable0044Ocelot 8.0.0-unstable00442018-07-11T05:38:24Z2018-12-15T06:16:54Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0043Ocelot 7.1.0-unstable00432018-07-11T05:31:50Z2018-12-15T06:16:51Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0042Ocelot 7.1.0-unstable00422018-07-10T17:15:27Z2018-12-15T06:16:51Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0041Ocelot 7.1.0-unstable00412018-07-10T17:06:43Z2018-12-15T06:16:52Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0040Ocelot 7.1.0-unstable00402018-07-09T17:39:30Z2018-12-15T06:16:55Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0039Ocelot 7.1.0-unstable00392018-07-09T07:18:06Z2018-12-15T06:16:52Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0038Ocelot 7.1.0-unstable00382018-07-08T14:12:55Z2018-12-15T06:16:54Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0037Ocelot 7.1.0-unstable00372018-07-08T14:06:37Z2018-12-15T06:16:54Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0036Ocelot 7.1.0-unstable00362018-07-05T06:01:18Z2018-12-15T06:16:55Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0035Ocelot 7.1.0-unstable00352018-07-02T19:52:42Z2018-12-15T06:16:56Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0034Ocelot 7.1.0-unstable00342018-07-01T08:00:12Z2018-12-15T06:16:55Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0033Ocelot 7.1.0-unstable00332018-06-29T18:13:20Z2018-12-15T06:16:56Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0031Ocelot 7.1.0-unstable00312018-06-27T17:22:01Z2018-12-15T06:16:47Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0030Ocelot 7.1.0-unstable00302018-06-22T15:41:02Z2018-12-15T06:16:47Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0029Ocelot 7.1.0-unstable00292018-06-22T06:05:28Z2018-12-15T06:16:55Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0028Ocelot 7.1.0-unstable00282018-06-21T21:50:57Z2018-12-15T06:16:49Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0027Ocelot 7.1.0-unstable00272018-06-20T21:46:35Z2018-12-15T06:16:47Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0026Ocelot 7.1.0-unstable00262018-06-20T19:49:19Z2018-12-15T06:16:49Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0025Ocelot 7.1.0-unstable00252018-06-19T20:01:12Z2018-12-15T06:16:50Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0023Ocelot 7.1.0-unstable00232018-06-17T18:29:47Z2018-12-15T06:16:50Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0022Ocelot 7.1.0-unstable00222018-06-15T19:35:14Z2018-12-15T06:16:47Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0020Ocelot 7.1.0-unstable00202018-06-12T05:13:02Z2018-12-15T06:16:50Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0019Ocelot 7.1.0-unstable00192018-06-11T22:03:36Z2018-12-15T06:16:50Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0017Ocelot 7.1.0-unstable00172018-06-11T19:28:20Z2018-12-15T06:16:52Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0016Ocelot 7.1.0-unstable00162018-06-11T19:09:38Z2018-12-15T06:16:49Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0014Ocelot 7.1.0-unstable00142018-06-08T15:04:18Z2018-12-15T06:16:51Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0013Ocelot 7.1.0-unstable00132018-06-08T14:59:44Z2018-12-15T06:16:50Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0012Ocelot 7.1.0-unstable00122018-06-06T07:56:31Z2018-12-15T06:16:53Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0011Ocelot 7.1.0-unstable00112018-05-31T21:13:29Z2018-12-15T06:16:53Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0010Ocelot 7.1.0-unstable00102018-05-24T22:00:20Z2018-12-15T06:16:57Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0009Ocelot 7.1.0-unstable00092018-05-24T21:49:12Z2018-12-15T06:16:50Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0007Ocelot 7.1.0-unstable00072018-05-22T22:36:41Z2018-12-15T06:16:54Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0006Ocelot 7.1.0-unstable00062018-05-22T05:40:12Z2018-12-15T06:16:52Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0005Ocelot 7.1.0-unstable00052018-05-17T06:50:07Z2018-12-15T06:18:41Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0002Ocelot 7.1.0-unstable00022018-05-15T17:36:19Z2018-12-15T06:18:41Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.1.0-unstable0001Ocelot 7.1.0-unstable00012018-05-14T20:30:26Z2018-12-15T06:18:41Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.0.9Ocelot 7.0.92018-07-09T18:30:49Z2018-12-15T06:18:41Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.0.8Ocelot 7.0.82018-07-08T14:21:45Z2018-12-15T06:18:48Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.0.7Ocelot 7.0.72018-07-02T19:12:48Z2018-12-15T06:18:43Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.0.6Ocelot 7.0.62018-06-22T06:42:32Z2018-12-15T06:18:45Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.0.5Ocelot 7.0.52018-06-12T05:55:49Z2018-12-15T06:18:43Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.0.4Ocelot 7.0.42018-05-17T18:22:17Z2018-12-15T06:18:44Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.0.3Ocelot 7.0.32018-05-15T20:48:26Z2018-12-15T06:18:44Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.0.1Ocelot 7.0.12018-05-14T20:46:11Z2018-12-15T06:18:44Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.0.0Ocelot 7.0.02018-05-11T07:18:16Z2018-12-15T06:18:48Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/7.0.0-unstable0024Ocelot 7.0.0-unstable00242018-05-11T07:04:10Z2018-12-15T06:18:48Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/6.1.0-unstable0019Ocelot 6.1.0-unstable00192018-05-09T17:57:08Z2018-12-15T06:18:48Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/6.0.0Ocelot 6.0.02018-04-30T18:36:12Z2018-12-15T06:18:47Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/6.0.0-unstable0064Ocelot 6.0.0-unstable00642018-04-30T18:00:40Z2018-12-15T06:18:44Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.6.0-unstable0032Ocelot 5.6.0-unstable00322018-04-30T09:34:41Z2018-12-15T06:18:47Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.6.0-unstable0031Ocelot 5.6.0-unstable00312018-04-30T09:27:35Z2018-12-15T06:18:48Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.6.0-unstable0030Ocelot 5.6.0-unstable00302018-04-26T20:06:29Z2018-12-15T06:18:52Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.6.0-unstable0029Ocelot 5.6.0-unstable00292018-04-26T08:46:38Z2018-12-15T06:18:47Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.6.0-unstable0028Ocelot 5.6.0-unstable00282018-04-25T15:54:16Z2018-12-15T06:18:45Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.6.0-unstable0027Ocelot 5.6.0-unstable00272018-04-24T07:36:10Z2018-12-15T06:18:47Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.6.0-unstable0025Ocelot 5.6.0-unstable00252018-04-22T11:10:06Z2018-12-15T06:18:50Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.6.0-unstable0024Ocelot 5.6.0-unstable00242018-04-20T20:34:34Z2018-12-15T06:18:50Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.6.0-unstable0023Ocelot 5.6.0-unstable00232018-04-18T19:42:30Z2018-12-15T06:18:51Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.6.0-unstable0022Ocelot 5.6.0-unstable00222018-04-18T14:29:50Z2018-12-15T06:18:51Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.6.0-unstable0021Ocelot 5.6.0-unstable00212018-04-18T07:52:23Z2018-12-15T06:18:51Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.6.0-unstable0020Ocelot 5.6.0-unstable00202018-04-18T07:36:57Z2018-12-15T06:18:44Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.6.0-unstable0006Ocelot 5.6.0-unstable00062018-04-17T21:11:57Z2018-12-15T06:18:44Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.6.0-unstable0005Ocelot 5.6.0-unstable00052018-04-17T18:31:50Z2018-12-15T06:18:45Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.6.0-unstable0004Ocelot 5.6.0-unstable00042018-04-14T05:45:12Z2018-12-15T06:18:44Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.6.0-unstable0003Ocelot 5.6.0-unstable00032018-04-07T20:59:59Z2018-12-15T06:18:51Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.6.0-unstable0002Ocelot 5.6.0-unstable00022018-04-12T16:43:01Z2018-12-15T06:18:48Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.6.0-unstable0001Ocelot 5.6.0-unstable00012018-04-08T14:59:06Z2018-12-15T06:18:47Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.5.7Ocelot 5.5.72018-04-25T21:02:58Z2018-12-15T06:18:48Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.5.6Ocelot 5.5.62018-04-25T08:48:34Z2018-12-15T06:18:48Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.5.5Ocelot 5.5.52018-04-22T11:28:44Z2018-12-15T06:19:52Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.5.4Ocelot 5.5.42018-04-21T07:06:53Z2018-12-15T06:18:47Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.5.3Ocelot 5.5.32018-04-19T07:02:56Z2018-12-15T06:18:48Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.5.2Ocelot 5.5.22018-04-12T17:20:34Z2018-12-15T06:18:48Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.5.1Ocelot 5.5.12018-04-08T16:43:43Z2018-12-15T06:18:50Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.5.0Ocelot 5.5.02018-04-07T21:11:37Z2018-12-15T06:18:48Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.4.0-unstable0004Ocelot 5.4.0-unstable00042018-04-07T20:30:37Z2018-12-15T06:18:47Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.4.0-unstable0003Ocelot 5.4.0-unstable00032018-04-07T11:07:47Z2018-12-15T06:18:48Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.4.0-unstable0002Ocelot 5.4.0-unstable00022018-04-06T09:18:35Z2018-12-15T06:18:48Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.4.0-unstable0001Ocelot 5.4.0-unstable00012018-04-02T17:17:54Z2018-12-15T06:18:49Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.3.1Ocelot 5.3.12018-04-02T18:39:57Z2018-12-15T06:18:53Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.3.0Ocelot 5.3.02018-03-24T09:59:19Z2018-12-15T06:18:53Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.3.0-unstable0004Ocelot 5.3.0-unstable00042018-03-23T18:06:49Z2018-12-15T06:18:48Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.3.0-unstable0003Ocelot 5.3.0-unstable00032018-03-22T08:36:14Z2018-12-15T06:18:53Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.3.0-unstable0002Ocelot 5.3.0-unstable00022018-03-21T06:35:34Z2018-12-15T06:18:50Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.2.0Ocelot 5.2.02018-03-20T21:07:31Z2018-12-15T06:18:48Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.2.0-unstable0001Ocelot 5.2.0-unstable00012018-03-20T20:53:33Z2018-12-15T06:18:50Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.1.0Ocelot 5.1.02018-03-18T15:29:37Z2018-12-15T06:18:50Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.1.0-unstable0010Ocelot 5.1.0-unstable00102018-03-18T15:03:33Z2018-12-15T06:18:51Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.1.0-unstable0009Ocelot 5.1.0-unstable00092018-03-17T18:16:03Z2018-12-15T06:18:51Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.1.0-unstable0008Ocelot 5.1.0-unstable00082018-03-17T18:11:42Z2018-12-15T06:18:52Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.1.0-unstable0007Ocelot 5.1.0-unstable00072018-03-17T13:05:20Z2018-12-15T06:18:51Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.1.0-unstable0006Ocelot 5.1.0-unstable00062018-03-17T11:39:32Z2018-12-15T06:18:48Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.1.0-unstable0005Ocelot 5.1.0-unstable00052018-03-16T17:53:41Z2018-12-15T06:18:53Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.1.0-unstable0004Ocelot 5.1.0-unstable00042018-03-14T19:59:41Z2018-12-15T06:18:48Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.1.0-unstable0002Ocelot 5.1.0-unstable00022018-03-13T20:35:59Z2018-12-15T06:18:51Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.1.0-unstable0001Ocelot 5.1.0-unstable00012018-03-10T21:28:30Z2018-12-15T06:19:49Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.0.1Ocelot 5.0.12018-03-13T20:46:30Z2018-12-15T06:18:47Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/5.0.0Ocelot 5.0.02018-03-10T21:20:04Z2018-12-15T06:20:09Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/4.1.0-unstable0001Ocelot 4.1.0-unstable00012018-03-10T21:06:50Z2018-12-15T06:20:09Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/4.0.0Ocelot 4.0.02018-03-09T07:54:08Z2018-12-15T06:20:10Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/4.0.0-unstable0013Ocelot 4.0.0-unstable00132018-03-09T07:41:17Z2018-12-15T06:20:12Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.2.0-unstable0044Ocelot 3.2.0-unstable00442018-03-08T20:43:55Z2018-12-15T06:20:12Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.2.0-unstable0040Ocelot 3.2.0-unstable00402018-03-08T07:36:12Z2018-12-15T06:20:13Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.2.0-unstable0039Ocelot 3.2.0-unstable00392018-03-05T20:23:53Z2018-12-15T06:20:10Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.2.0-unstable0038Ocelot 3.2.0-unstable00382018-03-04T10:27:53Z2018-12-15T06:20:11Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.2.0-unstable0037Ocelot 3.2.0-unstable00372018-03-04T10:06:53Z2018-12-15T06:20:10Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.2.0-unstable0033Ocelot 3.2.0-unstable00332018-03-03T17:20:32Z2018-12-15T06:20:10Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.2.0-unstable0018Ocelot 3.2.0-unstable00182018-03-03T15:27:57Z2018-12-15T06:20:13Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.2.0-unstable0017Ocelot 3.2.0-unstable00172018-03-02T18:08:33Z2018-12-15T06:20:07Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.2.0-unstable0016Ocelot 3.2.0-unstable00162018-03-02T18:03:29Z2018-12-15T06:20:08Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.2.0-unstable0015Ocelot 3.2.0-unstable00152018-03-02T17:54:57Z2018-12-15T06:20:15Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.2.0-unstable0013Ocelot 3.2.0-unstable00132018-03-02T17:50:31Z2018-12-15T06:20:08Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.2.0-unstable0012Ocelot 3.2.0-unstable00122018-03-02T17:20:16Z2018-12-15T06:20:14Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.2.0-unstable0009Ocelot 3.2.0-unstable00092018-03-02T17:10:24Z2018-12-15T06:20:12Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.2.0-unstable0008Ocelot 3.2.0-unstable00082018-03-02T10:30:15Z2018-12-15T06:20:09Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.2.0-unstable0007Ocelot 3.2.0-unstable00072018-03-01T13:03:40Z2018-12-15T06:20:08Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.2.0-unstable0006Ocelot 3.2.0-unstable00062018-02-27T09:06:46Z2018-12-15T06:20:08Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.2.0-unstable0005Ocelot 3.2.0-unstable00052018-02-27T08:51:47Z2018-12-15T06:20:10Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.2.0-unstable0004Ocelot 3.2.0-unstable00042018-02-27T08:26:56Z2018-12-15T06:20:09Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.2.0-unstable0002Ocelot 3.2.0-unstable00022018-02-21T20:58:43Z2018-12-15T06:20:11Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.2.0-unstable0001Ocelot 3.2.0-unstable00012018-02-15T09:57:58Z2018-12-15T06:21:10Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.1.9Ocelot 3.1.92018-03-04T10:24:04Z2018-12-15T06:20:11Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.1.8Ocelot 3.1.82018-03-03T15:46:29Z2018-12-15T06:20:10Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.1.7Ocelot 3.1.72018-03-01T13:16:01Z2018-12-15T06:20:15Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.1.6Ocelot 3.1.62018-02-21T21:12:38Z2018-12-15T06:20:14Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.1.5Ocelot 3.1.52018-02-15T10:21:19Z2018-12-15T06:20:14Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.1.4Ocelot 3.1.42018-02-14T20:25:12Z2018-12-15T06:20:09Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.1.0-unstable0012Ocelot 3.1.0-unstable00122018-02-14T19:07:55Z2018-12-15T06:20:14Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.1.0-unstable0010Ocelot 3.1.0-unstable00102018-02-13T23:05:26Z2019-01-09T07:44:56Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.1.0-unstable0007Ocelot 3.1.0-unstable00072018-02-13T09:12:05Z2018-12-15T06:20:09Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.1.0-unstable0006Ocelot 3.1.0-unstable00062018-02-12T18:58:04Z2018-12-15T06:20:09Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.1.0-unstable0005Ocelot 3.1.0-unstable00052018-02-08T18:09:04Z2018-12-15T06:20:14Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.1.0-unstable0004Ocelot 3.1.0-unstable00042018-02-03T11:05:12Z2018-12-15T06:20:14Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.1.0-unstable0003Ocelot 3.1.0-unstable00032018-02-02T11:11:44Z2018-12-15T06:20:14Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.1.0-unstable0002Ocelot 3.1.0-unstable00022018-02-01T20:05:23Z2018-12-15T06:20:14Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.1.0-unstable0001Ocelot 3.1.0-unstable00012018-02-01T13:57:18Z2018-12-15T06:20:11Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.0.3Ocelot 3.0.32018-02-13T14:44:05Z2018-12-15T06:20:13Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.0.2Ocelot 3.0.22018-02-05T19:18:20Z2018-12-15T06:20:11Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.0.1Ocelot 3.0.12018-02-02T13:29:20Z2018-12-15T06:20:12Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.0.0Ocelot 3.0.02018-01-31T21:16:27Z2018-12-15T06:20:11Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/3.0.0-unstable0059Ocelot 3.0.0-unstable00592018-01-31T20:46:15Z2018-12-15T06:20:11Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.1.0-unstable0058Ocelot 2.1.0-unstable00582018-01-31T20:40:26Z2018-12-15T06:20:13Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.1.0-unstable0057Ocelot 2.1.0-unstable00572018-01-27T20:08:30Z2018-12-15T06:20:14Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.1.0-unstable0056Ocelot 2.1.0-unstable00562018-01-22T20:26:19Z2018-12-15T06:20:15Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.1.0-unstable0055Ocelot 2.1.0-unstable00552018-01-18T21:07:38Z2018-12-15T06:20:13Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.1.0-unstable0053Ocelot 2.1.0-unstable00532018-01-16T07:15:35Z2018-12-15T06:20:13Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.1.0-unstable0052Ocelot 2.1.0-unstable00522018-01-13T06:13:54Z2018-12-15T06:20:10Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.1.0-unstable0051Ocelot 2.1.0-unstable00512018-01-10T18:55:17Z2018-12-15T06:20:11Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.1.0-unstable0050Ocelot 2.1.0-unstable00502018-01-10T18:22:06Z2018-12-15T06:20:13Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.1.0-unstable0049Ocelot 2.1.0-unstable00492018-01-10T08:23:58Z2018-12-15T06:20:12Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.1.0-unstable0048Ocelot 2.1.0-unstable00482018-01-10T08:17:11Z2018-12-15T06:20:13Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.1.0-unstable0047Ocelot 2.1.0-unstable00472018-01-06T16:43:55Z2018-12-15T06:20:11Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.1.0-unstable0046Ocelot 2.1.0-unstable00462018-01-05T21:54:08Z2018-12-15T06:20:09Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.1.0-unstable0045Ocelot 2.1.0-unstable00452018-01-05T21:31:47Z2018-12-15T06:20:13Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.1.0-unstable0044Ocelot 2.1.0-unstable00442018-01-02T18:53:55Z2018-12-15T06:20:15Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.1.0-unstable0043Ocelot 2.1.0-unstable00432018-01-01T18:45:05Z2018-12-15T06:20:13Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.1.0-unstable0042Ocelot 2.1.0-unstable00422017-12-18T22:18:18Z2018-12-15T06:20:13Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.1.0-unstable0041Ocelot 2.1.0-unstable00412017-12-12T07:49:29Z2018-12-15T06:20:15Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.1.0-unstable0037Ocelot 2.1.0-unstable00372017-12-09T14:46:00Z2018-12-15T06:20:13Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.1.0-unstable0036Ocelot 2.1.0-unstable00362017-12-06T08:28:28Z2018-12-15T06:21:15Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.0.11Ocelot 2.0.112018-01-22T20:43:27Z2018-12-15T06:20:11Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.0.10Ocelot 2.0.102018-01-10T20:11:16Z2018-12-15T06:21:34Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.0.8Ocelot 2.0.82018-01-06T16:54:39Z2018-12-15T06:21:34Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.0.7Ocelot 2.0.72018-01-05T22:06:31Z2018-12-15T06:21:38Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.0.6Ocelot 2.0.62018-01-02T19:13:52Z2018-12-15T06:21:40Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.0.5Ocelot 2.0.52018-01-01T19:02:01Z2018-12-15T06:21:40Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.0.4Ocelot 2.0.42017-11-25T15:17:17Z2018-12-15T06:21:39Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.0.3Ocelot 2.0.32017-11-22T07:34:52Z2018-12-15T06:21:40Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.0.2Ocelot 2.0.22017-11-19T21:20:09Z2018-12-15T06:21:37Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.0.1Ocelot 2.0.12017-11-15T08:28:47Z2018-12-15T06:21:35Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/2.0.0Ocelot 2.0.02017-11-01T17:18:15Z2018-12-15T06:21:35Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0158Ocelot 1.5.0-unstable01582017-10-13T07:10:15Z2018-12-15T06:21:37Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0154Ocelot 1.5.0-unstable01542017-10-09T12:35:55Z2018-12-15T06:21:37Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0151Ocelot 1.5.0-unstable01512017-10-09T10:34:06Z2018-12-15T06:22:40Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0149Ocelot 1.5.0-unstable01492017-09-12T14:29:07Z2018-12-15T06:21:40Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0147Ocelot 1.5.0-unstable01472017-08-30T17:29:54Z2018-12-15T06:21:39Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0144Ocelot 1.5.0-unstable01442017-07-19T22:06:12Z2018-12-15T06:21:40Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0134Ocelot 1.5.0-unstable01342017-07-04T18:48:20Z2018-12-15T06:21:37Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0133Ocelot 1.5.0-unstable01332017-07-04T18:45:01Z2018-12-15T06:21:38Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0131Ocelot 1.5.0-unstable01312017-07-04T18:18:02Z2018-12-15T06:21:39Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0130Ocelot 1.5.0-unstable01302017-06-30T08:36:04Z2018-12-15T06:21:35Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0122Ocelot 1.5.0-unstable01222017-06-29T05:57:21Z2018-12-15T06:21:34Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0115Ocelot 1.5.0-unstable01152017-06-25T21:17:59Z2018-12-15T06:21:40Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0111Ocelot 1.5.0-unstable01112017-06-24T12:17:10Z2018-12-15T06:21:38Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0107Ocelot 1.5.0-unstable01072017-06-17T13:48:15Z2018-12-15T06:22:39Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0103Ocelot 1.5.0-unstable01032017-06-16T15:07:45Z2018-12-15T06:21:37Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0079Ocelot 1.5.0-unstable00792017-05-09T19:42:37Z2018-12-15T06:22:45Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0072Ocelot 1.5.0-unstable00722017-04-28T12:07:38Z2018-12-15T06:22:44Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0071Ocelot 1.5.0-unstable00712017-04-23T14:45:30Z2018-12-15T06:21:39Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0067Ocelot 1.5.0-unstable00672017-04-21T15:26:48Z2018-12-15T06:21:39Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0059Ocelot 1.5.0-unstable00592017-04-16T18:48:34Z2018-12-15T06:22:45Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0053Ocelot 1.5.0-unstable00532017-03-19T16:00:04Z2018-12-15T06:21:39Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0043Ocelot 1.5.0-unstable00432017-03-19T12:51:29Z2018-12-15T06:21:40Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0039Ocelot 1.5.0-unstable00392017-03-18T08:08:56Z2018-12-15T06:21:41Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0033Ocelot 1.5.0-unstable00332017-03-15T18:39:54Z2018-12-15T06:21:37Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0031Ocelot 1.5.0-unstable00312017-03-14T18:57:44Z2018-12-15T06:21:41Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0029Ocelot 1.5.0-unstable00292017-03-12T22:50:09Z2018-12-15T06:22:43Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0028Ocelot 1.5.0-unstable00282017-03-12T22:41:16Z2018-12-15T06:21:34Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0027Ocelot 1.5.0-unstable00272017-03-12T10:48:18Z2018-12-15T06:21:37Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.5.0-unstable0004Ocelot 1.5.0-unstable00042017-03-07T13:21:29Z2018-12-15T06:22:36Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.20Ocelot 1.4.202017-10-13T10:09:30Z2018-12-15T06:21:37Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.11Ocelot 1.4.112017-10-09T14:31:42Z2018-12-15T06:21:37Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.10Ocelot 1.4.102017-08-30T19:39:27Z2018-12-15T06:21:34Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.9Ocelot 1.4.92017-06-30T08:45:03Z2018-12-15T06:21:42Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.8Ocelot 1.4.82017-06-29T06:13:30Z2018-12-15T06:21:41Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.7Ocelot 1.4.72017-06-25T21:26:33Z2018-12-15T06:21:37Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.6Ocelot 1.4.62017-06-24T12:25:54Z2018-12-15T06:22:37Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.5Ocelot 1.4.52017-06-19T22:50:47Z2018-12-15T06:21:39Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.4Ocelot 1.4.42017-04-28T12:18:28Z2018-12-15T06:21:39Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.3Ocelot 1.4.32017-04-27T07:57:22Z2018-12-15T06:21:36Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.2Ocelot 1.4.22017-04-16T19:00:46Z2018-12-15T06:22:39Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.1Ocelot 1.4.12017-03-07T13:27:24Z2018-12-15T06:21:38Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.0-unstable0110Ocelot 1.4.0-unstable01102017-03-06T02:31:12Z2018-12-15T06:21:37Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.0-unstable0108Ocelot 1.4.0-unstable01082017-03-05T17:47:17Z2018-12-15T06:21:37Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.0-unstable0107Ocelot 1.4.0-unstable01072017-03-05T17:45:00Z2018-12-15T06:21:37Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.0-unstable0106Ocelot 1.4.0-unstable01062017-03-05T17:42:45Z2018-12-15T06:21:37Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.0-unstable0105Ocelot 1.4.0-unstable01052017-03-05T17:40:19Z2018-12-15T06:21:37Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.0-unstable0104Ocelot 1.4.0-unstable01042017-03-05T17:38:03Z2018-12-15T06:21:37Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.0-unstable0103Ocelot 1.4.0-unstable01032017-03-05T17:35:51Z2018-12-15T06:21:40Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.0-unstable0102Ocelot 1.4.0-unstable01022017-03-05T17:10:34Z2018-12-15T06:21:39Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.0-unstable0092Ocelot 1.4.0-unstable00922017-02-26T10:47:23Z2018-12-15T06:21:39Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.0-unstable0091Ocelot 1.4.0-unstable00912017-02-25T19:28:10Z2018-12-15T06:21:36Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.0-unstable0090Ocelot 1.4.0-unstable00902017-02-25T19:22:35Z2018-12-15T06:21:36Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.0-unstable0089Ocelot 1.4.0-unstable00892017-02-25T19:20:21Z2018-12-15T06:21:40Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.0-unstable0064Ocelot 1.4.0-unstable00642017-02-21T17:52:00Z2018-12-15T06:21:39Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.0-unstable0058Ocelot 1.4.0-unstable00582017-02-17T20:24:39Z2018-12-15T06:23:05Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.0-unstable0056Ocelot 1.4.0-unstable00562017-02-17T18:26:47Z2018-12-15T06:23:06Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelothttps://www.nuget.org/packages/Ocelot/1.4.0-unstable0055Ocelot 1.4.0-unstable00552017-02-16T13:54:01Z2018-12-15T06:23:03Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelothttps://www.nuget.org/packages/Ocelot/1.4.0-unstable0051Ocelot 1.4.0-unstable00512017-02-15T07:10:32Z2018-12-15T06:23:02Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelothttps://www.nuget.org/packages/Ocelot/1.4.0-unstable0030Ocelot 1.4.0-unstable00302017-02-11T19:03:53Z2018-12-15T06:23:04Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelothttps://www.nuget.org/packages/Ocelot/1.4.0-unstable0026Ocelot 1.4.0-unstable00262017-02-11T12:44:04Z2018-12-15T06:23:03Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelothttps://www.nuget.org/packages/Ocelot/1.4.0-unstable0023Ocelot 1.4.0-unstable00232017-02-11T12:22:22Z2018-12-15T06:23:02Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelothttps://www.nuget.org/packages/Ocelot/1.4.0-set-up-admin-api0001Ocelot 1.4.0-set-up-admin-api00012017-02-15T13:26:16Z2018-12-15T06:23:05Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelothttps://www.nuget.org/packages/Ocelot/1.4.0-qos-documentatio0001Ocelot 1.4.0-qos-documentatio00012017-02-11T13:16:35Z2018-12-15T06:22:59Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelothttps://www.nuget.org/packages/Ocelot/1.4.0-pullrequest0047Ocelot 1.4.0-pullrequest00472017-02-17T20:21:57Z2018-12-15T06:22:59Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.0-pullrequest0039Ocelot 1.4.0-pullrequest00392017-02-11T19:01:46Z2018-12-15T06:23:02Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelothttps://www.nuget.org/packages/Ocelot/1.4.0-publish-unable-a0001Ocelot 1.4.0-publish-unable-a00012017-02-11T12:31:16Z2018-12-15T06:24:03Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelothttps://www.nuget.org/packages/Ocelot/1.4.0-nuget-package-de0001Ocelot 1.4.0-nuget-package-de00012017-02-17T20:19:46Z2018-12-15T06:23:05Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.4.0-beta0001Ocelot 1.4.0-beta00012017-03-07T13:13:35Z2018-12-15T06:23:03Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.3.3-pullrequest0054Ocelot 1.3.3-pullrequest00542017-02-20T20:44:06Z2018-12-15T06:23:09Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.3.2Ocelot 1.3.22017-02-17T20:31:23Z2018-12-15T06:23:05Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsThis project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.https://www.nuget.org/packages/Ocelot/1.3.2-pullrequest0045Ocelot 1.3.2-pullrequest00452017-02-15T20:27:52Z2018-12-15T06:23:03Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelothttps://www.nuget.org/packages/Ocelot/1.3.2-pullrequest0037Ocelot 1.3.2-pullrequest00372017-02-15T00:57:14Z2018-12-15T06:23:07Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelothttps://www.nuget.org/packages/Ocelot/1.3.1Ocelot 1.3.12017-02-07T20:26:31Z2018-12-15T06:24:07Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelothttps://www.nuget.org/packages/Ocelot/1.3.0-unstable0002Ocelot 1.3.0-unstable00022017-02-07T20:20:45Z2018-12-15T06:23:05Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelothttps://www.nuget.org/packages/Ocelot/1.2.0-unstable0033Ocelot 1.2.0-unstable00332017-02-06T22:25:59Z2018-12-15T06:23:05Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelothttps://www.nuget.org/packages/Ocelot/1.1.0Ocelot 1.1.02017-02-02T16:13:58Z2018-12-15T06:23:08Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelothttps://www.nuget.org/packages/Ocelot/1.1.0-beta0001Ocelot 1.1.0-beta00012017-02-02T15:59:32Z2018-12-15T06:23:06Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelothttps://www.nuget.org/packages/Ocelot/1.0.123Ocelot 1.0.1232017-01-29T09:43:09Z2018-12-15T06:23:09Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.122Ocelot 1.0.1222017-01-24T17:45:17Z2018-12-15T06:23:04Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.120Ocelot 1.0.1202017-01-21T10:23:38Z2018-12-15T06:23:03Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.117Ocelot 1.0.1172017-01-21T10:09:20Z2018-12-15T06:23:05Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.115-rc1Ocelot 1.0.115-rc12017-01-21T10:02:31Z2018-12-15T06:23:06Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.114-rc1Ocelot 1.0.114-rc12017-01-20T19:07:19Z2018-12-15T06:23:07Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.112-rc1Ocelot 1.0.112-rc12017-01-18T13:25:16Z2018-12-15T06:23:08Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.111-rc1Ocelot 1.0.111-rc12017-01-17T16:02:20Z2018-12-15T06:23:07Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.110-rc1Ocelot 1.0.110-rc12017-01-17T10:36:23Z2018-12-15T06:23:09Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.109-rc1Ocelot 1.0.109-rc12017-01-17T10:22:45Z2018-12-15T06:23:00Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.108-rc1Ocelot 1.0.108-rc12017-01-12T20:15:52Z2018-12-15T06:23:00Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.107-rc1Ocelot 1.0.107-rc12017-01-12T19:58:37Z2018-12-15T06:23:00Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.106-rc1Ocelot 1.0.106-rc12016-12-01T06:52:20Z2018-12-15T06:23:00Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.104-rc1Ocelot 1.0.104-rc12016-11-26T14:10:01Z2018-12-15T06:23:00Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.103-rc1Ocelot 1.0.103-rc12016-11-26T11:45:41Z2018-12-15T06:23:05Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.102-rc1Ocelot 1.0.102-rc12016-11-06T16:23:38Z2018-12-15T06:23:02Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.101-rc1Ocelot 1.0.101-rc12016-11-06T12:45:23Z2018-12-15T06:23:06Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.100-rc1Ocelot 1.0.100-rc12016-11-05T13:56:13Z2018-12-15T06:23:02Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.99-rc1Ocelot 1.0.99-rc12016-11-05T13:53:25Z2018-12-15T06:23:03Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.98-rc1Ocelot 1.0.98-rc12016-11-05T13:50:50Z2018-12-15T06:23:02Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.97-rc1Ocelot 1.0.97-rc12016-11-05T13:48:31Z2018-12-15T06:23:02Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.96-rc1Ocelot 1.0.96-rc12016-11-05T13:46:15Z2018-12-15T06:23:04Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.95-rc1Ocelot 1.0.95-rc12016-11-05T13:44:03Z2018-12-15T06:23:05Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.94-rc1Ocelot 1.0.94-rc12016-11-05T13:41:53Z2018-12-15T06:23:03Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.93-rc1Ocelot 1.0.93-rc12016-11-05T12:57:07Z2018-12-15T06:23:03Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.92-rc1Ocelot 1.0.92-rc12016-11-05T12:54:50Z2018-12-15T06:23:08Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.91-rc1Ocelot 1.0.91-rc12016-11-05T12:47:46Z2018-12-15T06:23:09Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.90-rc1Ocelot 1.0.90-rc12016-11-05T11:38:57Z2018-12-15T06:23:10Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.89-rc1Ocelot 1.0.89-rc12016-11-02T22:02:05Z2018-12-15T06:23:08Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.88-rc1Ocelot 1.0.88-rc12016-11-02T21:56:44Z2018-12-15T06:23:02Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.87-rc1Ocelot 1.0.87-rc12016-11-02T21:53:03Z2018-12-15T06:23:05Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.86-rc1Ocelot 1.0.86-rc12016-11-02T20:24:06Z2018-12-15T06:23:05Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.85-rc1Ocelot 1.0.85-rc12016-10-30T19:01:26Z2018-12-15T06:24:08Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.84-rc1Ocelot 1.0.84-rc12016-10-30T18:50:10Z2018-12-15T06:23:05Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.83-rc1Ocelot 1.0.83-rc12016-10-30T18:37:18Z2018-12-15T06:23:06Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.82-rc1Ocelot 1.0.82-rc12016-10-30T17:31:42Z2018-12-15T06:23:04Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.81-rc1Ocelot 1.0.81-rc12016-10-29T19:51:10Z2018-12-15T06:23:07Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.80-rc1Ocelot 1.0.80-rc12016-10-29T19:17:05Z2018-12-15T06:23:06Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.79-rc1Ocelot 1.0.79-rc12016-10-29T18:48:12Z2018-12-15T06:23:07Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.78-rc1Ocelot 1.0.78-rc12016-10-28T21:52:25Z2018-12-15T06:23:08Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.77-rc1Ocelot 1.0.77-rc12016-10-26T20:51:14Z2018-12-15T06:23:06Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.76-rc1Ocelot 1.0.76-rc12016-10-25T21:18:33Z2018-12-15T06:25:30Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.75-rc1Ocelot 1.0.75-rc12016-10-25T21:15:00Z2018-12-15T06:25:30Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.69-rc1Ocelot 1.0.69-rc12016-10-25T21:11:36Z2018-12-15T06:25:32Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.68-rc1Ocelot 1.0.68-rc12016-10-25T21:08:15Z2018-12-15T06:25:31Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.67-rc1Ocelot 1.0.67-rc12016-10-25T20:59:33Z2018-12-15T06:24:31Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.66-rc4Ocelot 1.0.66-rc42016-10-25T20:48:26Z2018-12-15T06:24:25Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.66-rc3Ocelot 1.0.66-rc32016-10-25T20:46:45Z2018-12-15T06:24:24Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.66-rc2Ocelot 1.0.66-rc22016-10-25T20:42:55Z2018-12-15T06:24:27Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.66-rc1Ocelot 1.0.66-rc12016-10-25T20:30:17Z2018-12-15T06:24:27Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.65-rc2Ocelot 1.0.65-rc22016-10-25T20:41:09Z2018-12-15T06:24:29Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.65-rc1Ocelot 1.0.65-rc12016-10-25T20:24:16Z2018-12-15T06:24:26Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/1.0.14-rc1Ocelot 1.0.14-rc12016-10-25T19:52:55Z2018-12-15T06:24:27Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/0.0.13-rc1Ocelot 0.0.13-rc12016-10-25T19:46:53Z2018-12-15T06:24:27Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gatewayhttps://www.nuget.org/packages/Ocelot/0.0.12-rc1Ocelot 0.0.12-rc12016-10-25T19:45:31Z2018-12-15T06:24:25Zmijitt0mhttps://www.nuget.org/profiles/mijitt0mraman-mhttps://www.nuget.org/profiles/raman-mThreeMammalshttps://www.nuget.org/profiles/ThreeMammalsOcelot Api Gateway