service-fabric-reverse-proxy | reverse proxy for accessing services | Proxy library

by spoorendonk C# Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | service-fabric-reverse-proxy Summary

service-fabric-reverse-proxy is a C# library typically used in Networking, Proxy, Jupyter, Docker applications. service-fabric-reverse-proxy has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

A reverse proxy for accessing services in a Service Fabric cluster. The reverse proxy is intended to behave like the reverse proxy available as a service in a hosted Service Fabric cluster. The use is meant for development environments on on-premise Service Fabric clusters, e.g., like the sample dev cluster running on Vagrant boxes, see blog post or github repo. The reverse proxy allows access to Service Fabric services that exposes HTTP endpoints. This provides a single point of entry for all services and a generic way to communicate between services. The proxy may be running on all nodes for high availability. For accessing the services in the cluster from the outside the proxy can be put behind another reverse proxy and load balancer such as nginx or HAProxy. The ServicePartitionResolver resolves the requested service partition closest to the proxy according to the documentation. The HTTP listener endpoints for a partition appears to be returned in a round-robin fashion.

Support

Quality

Security

License

Reuse

Support

service-fabric-reverse-proxy has a low active ecosystem.

It has 21 star(s) with 5 fork(s). There are 2 watchers for this library.

It had no major release in the last 6 months.

service-fabric-reverse-proxy has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of service-fabric-reverse-proxy is current.

Quality

service-fabric-reverse-proxy has 0 bugs and 1 code smells.

Security

service-fabric-reverse-proxy has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

service-fabric-reverse-proxy code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

service-fabric-reverse-proxy is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

service-fabric-reverse-proxy releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

It has 77 lines of code, 0 functions and 26 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of service-fabric-reverse-proxy

Get all kandi verified functions for this library.

service-fabric-reverse-proxy Key Features

No Key Features are available at this moment for service-fabric-reverse-proxy.

service-fabric-reverse-proxy Examples and Code Snippets

No Code Snippets are available at this moment for service-fabric-reverse-proxy.

Community Discussions

Trending Discussions on service-fabric-reverse-proxy

How to update Azure Service Fabric reverse proxy certificate

QUESTION

How to update Azure Service Fabric reverse proxy certificate

Asked 2017-Feb-28 at 10:33

I have my cluster setup with a reverse proxy set at port 8080. I now want to change the certificate used on the reverse proxy.

I added the new certificate to my KeyVault, and referenced it in vaultCertificates in the Microsoft.Compute/virtualMachineScaleSets ARM template. Pushed it, waited until it completed, RDP'd into each node and verified that the new certificate was installed.

I updated one of my front facing applications to use the new certificate and it worked fine (thus verifying that it could find it by the thumbprint).

I then modified reverseProxyCertificate.thumbprint in the Microsoft.ServiceFabric/clusters ARM template to reflect the new thumbprint. Pushed this and waited. And waited. And waited. After about an hour my cluster status went from "Updating" to "Ready" (although in my activity log the Write Clusters operation still says Started)

Now, when I go to https://{mycluster}.ukwest.cloudapp.azure.com:8080/ it is still serving up the old certificate.

I RDP'd into one of my nodes and opened up D:\SvcFab\FabricHostSettings.xml and under ApplicationGateway/Http, GatewayX509CertificateFindValue has the correct (new) value.

Looking here, I know it's for a local cluster, but it should be similar to one hosted on Azure, the last step is "Start and complete cluster upgrade". I can't find how, or if you're meant to, do this in Azure. I know for a fact that you can't just restart the VMSS, or it messes everything up!

Have I missed something?

...

ANSWER

Answered 2017-Feb-28 at 10:33

See:

https://github.com/ChackDan/Service-Fabric/tree/master/ARM%20Templates/ReverseProxySecureSample#configure-https-reverse-proxy-in-a-secure-cluster

Cluster must be initially created with RP cert that is different from cluster cert.

Source https://stackoverflow.com/questions/42272975

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install service-fabric-reverse-proxy

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: