carapaceproxy icon indicating copy to clipboard operation
carapaceproxy copied to clipboard

A Distributed Java Reverse Proxy

Results 95 carapaceproxy issues
Sort by recently updated
recently updated
newest added

As a sequel of #387, we need to introduce form for create/edit /delete for manul and static certificate.

enhancement

Authenticated origin pulls ensure requests to your origin server come from the Cloudflare network. More info here [(Authenticated origin pull)](https://developers.cloudflare.com/ssl/origin-configuration/authenticated-origin-pull/). Carapace side we will have to implement support both in...

To get an overview of certificates status, at the moment the only option available is to interface through the Admin interface. In some cases, however, it might be useful to...

enhancement

Following https://github.com/diennea/carapaceproxy/issues/241#issuecomment-842295085 we will start from Certificate page

When you call a url with a path that doesn't exist, it returns a page like: ![image](https://user-images.githubusercontent.com/43852233/159516403-a1e0f0f7-3344-4286-ad02-37d025ace338.png) We can go back to a better 404 page. For the root path...

Currently generation of wildcard certificate is done via route53. It would be useful to introduce support to DNS RFC 2136. - It is therefore necessary to have the possibility to...

enhancement
component/dynamiccertificates

Currently on Carapace we manage pages of 404 and internal server error (500). It is also not possible to handle a different page for other errors. It would be appropriate...

With many domains and certs the page is very slow to load: 1) add a "loading in progress" bar/symbol to let the user know that the certs are being loaded...

component/ui
component/dynamiccertificates

Switching a certificate from static to acme cannot be done painless up to now. Until the acme process hasn't finished the certificate cannot be served, even if still available as...

enhancement
component/ui
component/dynamiccertificates

It should be more useful to split existing _Total requests (Req)_ into: _Healthy req_ and _Failed req_ ones. Maybe we can even addo these metrics to grafana

component/ui
component/core
component/api