3.30 — Add HTTP/S proxy entry

From SparkView version 6.4, the HTTP proxy has been completely redesigned to be faster, more secure and more accessible. The handling is fundamentally different from previous versions and there are a few important things to note:

The URL structure before version 6.4 was https://yourgateway.com/PXY/serverId. Now virtual hosts are used, resulting in the following structure: https://serverid.yourgateway.com.
This means that a domain name must be used for the SparkView gateway if the HTTP proxy is to be used.
Your own DNS server must have a wildcard entry on the same IP address as the gateway itself: *.yourgateway.com
To test the feature without a DNS server, the hosts file of the server/computer can be modified. Host file locations:
- Windows: %windir%\system32\drivers\etc\hosts
- Linux: /etc/hosts
- macOS: /etc/hosts or /private/etc/hosts
- Example:
```
192.168.10.4    sparkview.local
192.168.10.4    serverid.sparkview.local
192.168.10.4    server2id.sparkview.local
```

To add an HTTP/S proxy target, the above requirements must be met and the server must be added via config.html and the Servers tab (see chapter 4.1).

1.1 – Features

1.2 – Architecture

1.3 – What's the difference

2.1 – Install J2SE Software Development Kit (JDK)

2.2 – Install as a Windows service

2.3 – Install as Linux/Unix daemon

2.4 – Install as macOS daemon

2.5 – Install HTML client on other web servers

2.6 – Run SparkView as a container (Docker)

2.7 – Install as PWA

2.8 – Integrating a license

3.1 – Gateway

3.2 – HTTPS and WSS (WebSocket secure connection)

3.3 – Remote Desktop Web Access Portal Integration

3.4 – Servers & RDP options

3.5 – Users

3.6 – Easy printing

3.7 – RemoteApp and start a program instead of the whole desktop

3.8 – Clipboard redirection and shared clipboard

3.9 – Bidirectional audio redirection (RDP)

3.10 – File share (uploading and downloading)

3.11 – Session Recording and Playback

3.12 – Session Shadowing (join or share an active session on gateway)

3.13 – Native RDP shadowing (join any active RDP sessions)

3.14 – Touch interface (iOS, Android etc)

3.15 – Touch remoting

3.16 – Hyper-V Console and Enhanced Session Mode

3.17 – RDP connection cache/pool

3.18 – Symlink (access link)

3.19 – Macro recording

3.20 - Remote assistance

3.21 – RFB (VNC) protocol support

3.22 – SSH and Telnet

3.23 – Smart Card Redirection

3.24 – Scanner redirection

3.25 – USB redirection

3.26 – OAuth 2.0/Okta integration

3.27 – Active Directory, Azure AD, LDAP, RADIUS integration

3.28 – Using Java parameters

3.29 – Send logs to syslog

3.30 — Add HTTP/S proxy entry

4.1 – config.html

4.2 – file.html

4.3 – join.html

4.4 – login.html

4.5 – player.html

4.6 – rdp.html

4.7 – report.html

4.8 – shadow.html

4.9 – ssh.html

4.10 – telnet.html

4.11 – vnc.html

4.12 – Further files and views

5.1 – Session management

5.2 – Multi-Monitor

5.3 – SMB2 and SFTB file proxy

5.4 – Deploy, run and test applications in the cloud

5.5 – IP filter (iptables)

5.6 – SNMP integration

5.7 – SSH authentication with keys

6.1 – Reporting API (query server status, client side JavaScript API)

6.2 – RDP library (client side JavaScript API)

6.2.1 – RDP parameters

6.2.2 – Passing parameters via URL (Connection String)

6.2.3 – Passing parameter via object or cookie

6.2.4 – Usage of RDP class

6.2.5 – Extend RDP: Virtual Channel and Dynamic Virtual Channel

6.2.6 – Extend Gateway: Gateway Channel

6.3 – Plug-ins (server side Java API)

6.4 – HTTP Request API (server side)

7.1 – Reverse Agent: Getting started

Appendix A – Shortcut keys

Appendix B – Browser support

Appendix C – EchoHandler and network check

Appendix D – configuration example for nginx

Appendix E – configuration example for Apache Proxy

Appendix F – configuration for Juniper, Cisco, Dell etc SSL VPN

Appendix G – SMB path

Appendix H – Ping

Appendix I – TrustStore