Skip to content

Commit 62eeb54

Browse files
Split upstream/downstream
1 parent 311fd6f commit 62eeb54

6 files changed

Lines changed: 29 additions & 9 deletions

File tree

modules/ROOT/pages/_partials/task-add-api-instance.adoc

Lines changed: 24 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -152,8 +152,8 @@ NOTE: Anypoint API Manager supports OpenAPI Specification (OAS) 3.0, with the ex
152152
. Click *Next*.
153153
//end::soap[]
154154

155-
// Endpoint for Mule proxies
156-
//tag::proxy-endpoints[]
155+
// Mule proxies downstream
156+
//tag::proxy-downstream[]
157157

158158
. Configure the downstream configuration settings:
159159
+
@@ -164,6 +164,27 @@ include::partial$api-configuration-tables.adoc[tags=mule-proxy-downstream]
164164
====
165165

166166
. Click *Next*.
167+
//end::proxy-downstream[]
168+
169+
// HTTPS Mule proxies downstream
170+
//tag::https-proxy-downstream[]
171+
172+
. Configure the downstream configuration settings:
173+
+
174+
.Expand for configuration settings.
175+
[%collapsible]
176+
====
177+
include::partial$api-configuration-tables.adoc[tags=mule-proxy-downstream]
178+
====
179+
+
180+
NOTE: To configure an HTTPS Proxy, you must select *HTTPS* and configure an *Inbound TLS* context.
181+
182+
. Click *Next*.
183+
//end::https-proxy-downstream[]
184+
185+
// Mule proxies upstream
186+
//tag::proxy-downstream[]
187+
167188
. Configure the upstream configuration settings:
168189
+
169190
.Expand for configuration settings.
@@ -172,8 +193,7 @@ include::partial$api-configuration-tables.adoc[tags=mule-proxy-downstream]
172193
include::partial$api-configuration-tables.adoc[tags=mule-proxy-upstream]
173194
====
174195

175-
. Click *Next*.
176-
//end::proxy-endpoints[]
196+
//end::proxy-upstream[]
177197

178198
// Steps to save
179199
//tag::last-steps[]

modules/ROOT/pages/building-https-proxy.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Set TLS context's target to *Mule*.
3232

3333
Configure your HTTPS API Proxy by completing the following tasks:
3434

35-
include::partial$task-add-api-instance.adoc[tags=proxy-first-steps;target-type;mid-steps;asset-type-options;proxy-endpoints;last-steps]
35+
include::partial$task-add-api-instance.adoc[tags=proxy-first-steps;target-type;mid-steps;asset-type-options;https-proxy-downstream;proxy-upstream;last-steps]
3636

3737

3838
== API Proxy Deployment

modules/ROOT/pages/building-soap-proxy.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ With SOAP proxy v2.1.0, you can retrieve a WSDL from a remote location using the
4646

4747
Configure your SOAP proxy by completing the following steps:
4848

49-
include::partial$task-add-api-instance.adoc[tags=proxy-first-steps;target-type;mid-steps;soap;proxy-endpoints;last-steps]
49+
include::partial$task-add-api-instance.adoc[tags=proxy-first-steps;target-type;mid-steps;soap;proxy-downstream;proxy-upstream;last-steps]
5050

5151

5252
== Troubleshooting SOAP Proxies for Missing Imports on XSD Files

modules/ROOT/pages/proxy-deploy-raml-oas-proxy.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ API Manager 2.x enables you to use a RAML or OAS type of API Proxy, for all your
66

77
Configure your RAML or OAS API proxy by completing the following steps:
88

9-
include::partial$task-add-api-instance.adoc[tags=proxy-first-steps;target-type;mid-steps;raml-oas;proxy-endpoints;last-steps]
9+
include::partial$task-add-api-instance.adoc[tags=proxy-first-steps;target-type;mid-steps;raml-oas;proxy-downstream;proxy-upstream;last-steps]
1010

1111

1212
== See Also

modules/ROOT/pages/proxy-domain-support.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ For HTTP listener configuration defined in the domain, the listener setup on the
4242

4343
To configure the API proxy domain by completing the following steps:
4444

45-
include::partial$task-add-api-instance.adoc[tags=proxy-first-steps;hybrid;mid-steps;asset-type-options;proxy-endpoints;last-steps]
45+
include::partial$task-add-api-instance.adoc[tags=proxy-first-steps;hybrid;mid-steps;asset-type-options;proxy-downstream;proxy-upstream;last-steps]
4646

4747
. After saving the API proxy configuration, perform one of the following steps:
4848

modules/ROOT/pages/proxy-latest-concept.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ For Mule versions 3.8 and later, use Mule Agent 1.9.0. For Mule 4.x, use the Mul
2727

2828
Deploy your proxy by completing the following steps:
2929

30-
include::partial$task-add-api-instance.adoc[tags=proxy-first-steps;target-type;mid-steps;asset-type-options;proxy-endpoints;last-steps]
30+
include::partial$task-add-api-instance.adoc[tags=proxy-first-steps;target-type;mid-steps;asset-type-options;proxy-downstream;proxy-upstream;last-steps]
3131

3232
If you are deploying your API to a Mule 4 environment and want to enable the proxy to support HTTPS requests, first xref:building-https-proxy.adoc[build HTTPS API proxies].
3333

0 commit comments

Comments
 (0)