[db-wg] Removing Apache Proxy Servers from DB Services

Dear Colleagues,

We have now removed the Apache httpd proxy servers from in front of our production services.

If you are having any problems following this change, please contact me directly or open a ticket with <ripe-dbm at ripe.net> .

Regards
Ed Shryane
RIPE NCC



> On 22 Feb 2022, at 16:07, Edward Shryane via db-wg <db-wg at ripe.net> wrote:
> 
> Dear Colleagues,
> 
> Next Tuesday, 1st March, the DB team plan to remove the Apache httpd proxy servers for the following services:
> 
> * https://apps.db.ripe.net/
> * https://rdap.db.ripe.net/
> * https://rest.db.ripe.net/
> * https://syncupdates.db.ripe.net/
> 
> This will allow us to simplify our production environment, reducing operational work and maintenance.
> 
> Be aware that URL validation will be stricter after this change. For example, the following will return a 400 Bad Request:
> * Empty path segments (i.e. '//')
> * Encoded path separators (i.e. %2F for '/')
> * Encoded query separator (i.e. %3F for '?')
> 
> Please test your client using the TEST environment: https://www.ripe.net/manage-ips-and-asns/db/ripe-test-database
> or the Release Candidate environment: https://www.ripe.net/manage-ips-and-asns/db/release-notes/rc-release-candidate-environment
> 
> Regards
> Ed Shryane
> RIPE NCC
>