UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36

Steps to reproduce the problem:
1. Start Chromium with the following command (used by Puppeteer) pointing to an empty data dir:

chromium-browser --disable-background-networking --disable-background-timer-throttling --disable-client-side-phishing-detection --disable-default-apps --disable-extensions --disable-hang-monitor --disable-popup-blocking --disable-prompt-on-repost --disable-sync --disable-translate --metrics-recording-only --no-first-run --safebrowsing --disable-auto-update --enable-automation --password-store=basic --use-mock-keychain --remote-debugging-port=0 --user-data-dir=/tmp/test_redirect --disable-gpu --hide-scrollbars --mute-audio --window-size=2560,1440

2. Navigate to a website that returns a 302 redirect after a POST, for example any airline website like https://www.singaporeair.com/en_UK/gb/home

3. Search for a flight.

4. The request to https://www.singaporeair.com/booking-flow.form should return a 302 but it hangs indefinitely.

What is the expected behavior?
The redirect should be handled properly.

What went wrong?
The browser stays in a waiting state indefinitely. I have identified that this started failing on Chromium 63.0.3239.0 but it worked on Chromium 62.0.3202.0 repeating the steps above. Any other version after Chromium Chromium 63.0.3239.0 exposes the same behaviour.

To add more information, if the --headless argument is passed then the redirect is followed correctly (but https://www.singaporeair.com bot protection kicks in and a CAPTCHA is displayed blocking the navigation).

Did this work before? Yes 62.0.3202.0

Chrome version: 64.0.3282.167  Channel: stable
OS Version: Ubuntu 16.04
Flash Version: