View Attach (4) Info

Add new attachment

Only authorized users are allowed to upload new attachments.

List of attachments

Kind Attachment Name Size Version Date Modified Author Change note
png
 dmz_port.png 54.9 kB 2 25-Oct-2018 04:31 Ben Spink
png
 dmz_publickey.png 13.9 kB 1 25-Oct-2018 04:31 Ben Spink
png
 dmz_selector.png 30.3 kB 1 25-Oct-2018 04:31 Ben Spink
png
 dmz_user.png 57.6 kB 3 25-Oct-2018 04:31 Ben Spink

This page (revision-31) was last changed on 24-Mar-2020 03:28 by Ben Spink

This page was created on 25-Oct-2018 04:31 by Ben Spink

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 38 changed one line
When a connection comes into the DMZ server over SFTP/FTP(es)/HTTP(s)/WebDAV(s), the DMZ server talks to the internal server on an existing connection it already has from the internal server. This communication is over a SSL socket always initiated from the internal to the DMZ. The protocol the DMZ then uses inside this secure connection is HTTP. The internal server then attaches the connection to the first HTTP (not HTTPS) port internally that it finds in its list of ports. So all interaction between DMZ and Internal is the HTTP protocol (inside a SSL connection). The user may be using SFTP to connect to the DMZ, and ask for a directory listing. This then results in the DMZ asking the internal for a dir listing using HTTP, and then its translated and delivered to the SFTP client as a SFTP dir listing. This way all protocols are handled byt the DMZ, and the internal server does everything using one protocol that can handle anything the DMZ needs.
When a connection comes into the DMZ server over SFTP/FTP(es)/HTTP(s)/WebDAV(s), the DMZ server talks to the internal server on an existing connection it already has from the internal server. This communication is over a SSL socket always initiated from the internal to the DMZ. The protocol the DMZ then uses inside this secure connection is HTTP. The internal server then attaches the connection to the first HTTP (not HTTPS) port internally that it finds in its list of ports.
So all interaction between DMZ and Internal is the HTTP protocol (inside a SSL connection). The user may be using SFTP to connect to the DMZ, and ask for a directory listing. This then results in the DMZ asking the internal server for a dir listing using HTTP, and then its translated and delivered to the SFTP client as a SFTP dir listing. This way all protocols are handled by the DMZ, and the internal server does everything using one protocol that can handle everything.
----
!No prefs are stored on the DMZ server.
!No users are stored on the DMZ server.
!No user data files are stored on the DMZ server.
!File transfers are streamed through to the Internal server.
Version Date Modified Size Author Changes ... Change note
31 24-Mar-2020 03:28 7.887 kB Ben Spink to previous
30 26-Feb-2020 16:31 5.528 kB Halmágyi Árpád to previous | to last
29 21-Jan-2020 11:00 5.527 kB Halmágyi Árpád to previous | to last
28 21-Feb-2019 19:23 5.416 kB Ada Csaba to previous | to last
27 21-Feb-2019 19:23 5.414 kB Ada Csaba to previous | to last
26 25-Oct-2018 04:31 4.72 kB Ben Spink to previous | to last
25 25-Oct-2018 04:31 4.639 kB Ben Spink to previous | to last
24 25-Oct-2018 04:31 4.654 kB Ben Spink to previous | to last
23 25-Oct-2018 04:31 4.644 kB Ben Spink to previous | to last
22 25-Oct-2018 04:31 4.648 kB Halmágyi Árpád to previous | to last
21 25-Oct-2018 04:31 4.64 kB Ben Spink to previous | to last
« This page (revision-31) was last changed on 24-Mar-2020 03:28 by Ben Spink
G’day (anonymous guest)
CrushFTP9 | What's New

Referenced by
Enterprise License Enhancements
High Availability
LeftMenu

JSPWiki