New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[gateway] Be able to configure finely HTTP / HTTPS / Proxy per endpoint #242

Closed
brasseld opened this Issue Oct 6, 2016 · 0 comments

Comments

Projects
None yet
2 participants
@brasseld
Member

brasseld commented Oct 6, 2016

Currently, when you have a set of endpoints for a given API, they are all sharing the same "http" configuration meaning that they are sharing the same http / https and proxy configuration.

In some case, when we are doing a kind of "Mashup" API we need to configure endpoint individually because for some of them we need https or proxy but not for the others.

@brasseld brasseld self-assigned this Oct 6, 2016

brasseld added a commit to gravitee-io/gravitee-gateway-api that referenced this issue Oct 6, 2016

brasseld added a commit to gravitee-io/gravitee-definition that referenced this issue Oct 6, 2016

brasseld added a commit to gravitee-io/gravitee-gateway that referenced this issue Oct 6, 2016

brasseld added a commit to gravitee-io/gravitee-management-webui that referenced this issue Oct 6, 2016

brasseld added a commit to gravitee-io/gravitee-management-rest-api that referenced this issue Oct 6, 2016

brasseld added a commit to gravitee-io/gravitee-management-rest-api that referenced this issue Oct 7, 2016

brasseld added a commit to gravitee-io/gravitee-management-webui that referenced this issue Oct 7, 2016

brasseld added a commit to gravitee-io/gravitee-definition that referenced this issue Oct 10, 2016

brasseld added a commit to gravitee-io/gravitee-management-webui that referenced this issue Oct 10, 2016

@brasseld brasseld added this to the 1.0.0 milestone Oct 10, 2016

brasseld added a commit to gravitee-io/gravitee-gateway that referenced this issue Oct 10, 2016

brasseld added a commit to gravitee-io/gravitee-management-webui that referenced this issue Oct 10, 2016

brasseld added a commit to gravitee-io/gravitee-gateway-api that referenced this issue Oct 10, 2016

brasseld added a commit to gravitee-io/gravitee-gateway that referenced this issue Oct 10, 2016

brasseld added a commit to gravitee-io/gravitee-management-webui that referenced this issue Oct 11, 2016

brasseld added a commit to gravitee-io/gravitee-management-webui that referenced this issue Oct 12, 2016

tcompiegne added a commit to gravitee-io/gravitee-management-webui that referenced this issue Oct 12, 2016

tcompiegne added a commit to gravitee-io/gravitee-management-webui that referenced this issue Oct 12, 2016

tcompiegne added a commit to gravitee-io/gravitee-management-webui that referenced this issue Oct 12, 2016

tcompiegne added a commit to gravitee-io/gravitee-definition that referenced this issue Oct 12, 2016

tcompiegne added a commit to gravitee-io/gravitee-gateway-api that referenced this issue Oct 12, 2016

tcompiegne added a commit to gravitee-io/gravitee-gateway that referenced this issue Oct 12, 2016

tcompiegne added a commit to gravitee-io/gravitee-management-rest-api that referenced this issue Oct 12, 2016

tcompiegne added a commit to gravitee-io/gravitee-management-webui that referenced this issue Oct 12, 2016

feat(gateway): Define HTTP / HTTPS or proxy per endpoint instead of g… (
#223)

* feat(gateway): Define HTTP / HTTPS or proxy per endpoint instead of globally for an API

Closes gravitee-io/issues#242
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment