many-ocean-31725
10/08/2020, 9:39 AMAuthorization
header. And the token is not checking out as a proper JWT token, just some base64 encoded (seemingly) random data. Any ideas?
Here is also the request data from the browser:
Request headers:
GET / HTTP/1.1
Host: 127.0.0.1:4455
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:82.0) Gecko/20100101 Firefox/82.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Referer: <http://127.0.0.1:4455/auth/registration?request=03dcb39d-a07d-4acd-8c9d-0c59dfbb6ecb>
DNT: 1
Connection: keep-alive
Cookie: ory_kratos_session=MTYwMjE0OTQ0NnxEdi1CQkFFQ180SUFBUkFCRUFBQVFmLUNBQUVHYzNSeWFXNW5EQVVBQTNOcFpBWnpkSEpwYm1jTUpnQWtaV1ZrTkRWaE9UUXRaRFptTUMwME5HSmxMVGs0TURJdE5USTJZV1ZsTXpVd1pEQml8Mpc5oSud9c6tE092JAolh4AgCRLKejDZbre0uEzlTrg=
Upgrade-Insecure-Requests: 1
Pragma: no-cache
Cache-Control: no-cache
Response headers:
HTTP/1.1 200 OK
X-Powered-By: Express
Content-Type: text/html; charset=utf-8
Content-Length: 14314
ETag: W/"37ea-tsGGjwixWD3TYcue/gXHOluju+E"
Date: Thu, 08 Oct 2020 09:30:46 GMT
Connection: keep-alive