form submissions result in 302 redirect with query string absent
I've created a GitLab Pages site using Hugo that includes a search bar powered by FuseJS.
The basic setup right now adds a search form with action="/search" method="get"
which does as you'd expect: It submits the search query appended as a query string to the URI, i.e. /search/?s=about
.
The same setup has been tested on both Netlify and GitHub Pages and is working fine.
In GitLab Pages, however, that search query is lost from the URI following that 302 response and a redirect.
Here's what I'm seeing in the Header info in Chrome dev tools:
# General
Request URL: https://thombruce.gitlab.io/search?s=about
Request Method: GET
Status Code: 302
Remote Address: 35.185.44.232:443
Referrer Policy: no-referrer-when-downgrade
# Response Headers
content-length: 52
content-type: text/html; charset=utf-8
date: Fri, 04 Jan 2019 16:36:58 GMT
location: //thombruce.gitlab.io/search/
status: 302
vary: Origin
# Request Headers
:authority: thombruce.gitlab.io
:method: GET
:path: /search?s=about
:scheme: https
accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8
accept-encoding: gzip, deflate, br
accept-language: en-US,en;q=0.9
cache-control: no-cache
cookie: [REDACTED]
pragma: no-cache
referer: https://thombruce.gitlab.io/search/
upgrade-insecure-requests: 1
user-agent: Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Mobile Safari/537.36
# Query String Parameters
s: about
Having compared against GitHub Pages, my first thought is: Does this have something to do with the location
response header? GH has the same header, but query string there is preserved.