v5.8.1-rc3

Fixes:

• #2770: The proxy to the feature-api webapp always used localhost as hostname, which does not work when feature-api is deployed under a virtual host. This fix adds a flamingo.restproxy.host init parameter to the viewer webapp configure the hostname to the feature-api webapp. Note that the feature-api itself does not perform any localhost security checks, the Tomcat HTTP connector must only be listening to localhost! In addition, the hostname must resolve to 127.0.0.1 on the server itself, not a public IP address. The hostname should be added to the hostfile on the server (/etc/hosts). The init-parameter can be configured in viewer/META-INF/context.xml as follows:

  <Parameter name="flamingo.restproxy.host" override="false" value="[the hostname here]"/>  
  <Parameter name="flamingo.restproxy.port" override="false" value="8081"/>

v5.9.7

[maven-release-plugin] copy for tag v5.9.7

v5.9.6

[maven-release-plugin] copy for tag v5.9.6

v5.9.5

[maven-release-plugin] copy for tag v5.9.5

v5.9.2

NB. in deze versie kan er geen gebruik worden gemaakt van Oracle als configuratie database en misschien ook niet van SQL Server

v5.9.4

[maven-release-plugin] copy for tag v5.9.4

v5.8.1-rc2

[maven-release-plugin] copy for tag v5.8.1-rc2

v5.8.1-rc1

[maven-release-plugin] copy for tag v5.8.1-rc1

v5.9.3

[maven-release-plugin] copy for tag v5.9.3

v5.9.1

[maven-release-plugin] copy for tag v5.9.1