@@ -216,22 +216,25 @@ $ helm install kubernetes/samples/charts/ingress-per-domain \
216
216
e. To confirm that the load balancer noticed the new Ingress and is successfully routing to the domain's server pods,
217
217
you can hit the URL for the "WebLogic Ready App" which will return a HTTP 200 status code, as
218
218
shown in the example below. If you used the host-based routing Ingress sample, you will need to
219
- provide the hostname in the ` -H ` option:
219
+ provide the hostname in the ` -H ` option.
220
+
221
+ ** NOTE** : Be sure to include the trailing forward slash on the URL, otherwise the command won't work.
222
+
220
223
```
221
- $ curl -v -H 'host: sample-domain1.org' http://your.server.com:30305/weblogic/
222
- *
About to connect() to your.server.com port 30305 (#0)
223
- * Trying 10.196.1.64...
224
+ $ curl -v -H 'host: sample-domain1.org' http://your.server.com:30305/weblogic/
225
+ * About to connect() to your.server.com port 30305 (#0)
226
+ * Trying 10.196.1.64...
224
227
* Connected to your.server.com (10.196.1.64) port 30305 (#0)
225
-
> GET /weblogic/ HTTP/1.1
226
- > User-Agent: curl/7.29.0
227
- > Accept: */*
228
- > host: domain1.org
228
+ > GET /weblogic/ HTTP/1.1
229
+ > User-Agent: curl/7.29.0
230
+ > Accept: */*
231
+ > host: domain1.org
229
232
>
230
-
< HTTP/1.1 200 OK
231
- < Content-Length: 0
233
+ < HTTP/1.1 200 OK
234
+ < Content-Length: 0
232
235
< Date: Thu, 20 Dec 2018 14:52:22 GMT
233
-
< Vary: Accept-Encoding
234
- <
* Connection #0 to host your.server.com left intact
236
+ < Vary: Accept-Encoding
237
+ < * Connection #0 to host your.server.com left intact
235
238
```
236
239
** Note** : Depending on where your Kubernetes cluster is running, you may need to open firewall ports or
237
240
update security lists to allow ingress to this port.
0 commit comments