| ... |
... |
@@ -6,9
+6,9 @@ |
| 6 |
6 |
|
| 7 |
7 |
The problematic scenario (see figure) is the following: |
| 8 |
8 |
|
| 9 |
|
-1. The user calls the URL {{code language="none"}}https://www.example.com/formcycle{{{/code}}}. |
|
9 |
+1. The user calls the URL {{code language="none"}}https://www.example.com/formcycle{{/code}}. |
| 10 |
10 |
1. The request is received and evaluated by the intermediate server. |
| 11 |
|
-1. The intermediate server makes a new request to the designated server. However, since an internal request is made here, the call URL is changed to {{code language="none"}}http://192.168.0.1/formcycle{{{/code}}}. This URL now arrives at the application server and no longer contains the required information about which URL was actually called by the user. |
|
11 |
+1. The intermediate server makes a new request to the designated server. However, since an internal request is made here, the call URL is changed to {{code language="none"}}http://192.168.0.1/formcycle{{/code}}. This URL now arrives at the application server and no longer contains the required information about which URL was actually called by the user. |
| 12 |
12 |
|
| 13 |
13 |
{{info}} |
| 14 |
14 |
Since {{formcycle/}} interprets the original request URL of the user, especially when logging into a form, and this URL may not be determined correctly, it is necessary to configure intermediate servers accordingly. Make sure that both the HTTP header //Host// and the protocol used (//HTTP //or //HTTPS//) are forwarded unchanged. |
| ... |
... |
@@ -18,7
+18,7 @@ |
| 18 |
18 |
|
| 19 |
19 |
For the correct configuration of an Apache server, which acts as a reverse proxy, two points are relevant and have to be stored e.g. in the configuration of the VirtualHosts: |
| 20 |
20 |
|
| 21 |
|
-1. The instruction {{{code language="none"}}}ProxyPreserveHost On{{{/code}} to get the originally called //Host// header |
|
21 |
+1. The instruction {{code language="none"}}ProxyPreserveHost On{{/code}} to get the originally called //Host// header |
| 22 |
22 |
1. The separation of the individual protocols and its usage when forwarding to the application server. This means that for //HTTP// and //HTTPS// a separate VirtualHost with appropriate configuration must be used. |
| 23 |
23 |
|
| 24 |
24 |
This configuration, as well as any settings that may be necessary when using self-generated certificates, is briefly illustrated here: |