[Bug]: Response headers does not have Location value

[gokulsam07]

Version

1.45.0

Steps to reproduce

test('Validate login', async ({ request }) => {
const loginForm = {
email: 'Admin',
password: 'admin123'
};
const response = await request.post('https://opensource-demo.orangehrmlive.com/web/index.php/auth/validate', {multipart: loginForm})
console.log(response.headers());
expect(response.ok()).toBeTruthy();
expect(response.headers()['Location']).toContain('auth/login');
})

Response in trace viewer:

Server: nginx
Date: Thu, 27 Jun 2024 05:16:30 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: close
Set-Cookie: orangehrm=89519dac5d4d3b945de9ed7b236a617d; path=/web; secure; HttpOnly; SameSite=Lax
Cache-Control: no-cache, private
Location: https://opensource-demo.orangehrmlive.com/web/index.php/auth/login
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Strict-Transport-Security: max-age=63072000; includeSubdomains;
Content-Security-Policy: default-src blob: 'self' *.projects-abroad.net fonts.googleapis.com www.google.com fonts.gstatic.com code.jquery.com maxcdn.bootstrapcdn.com ajax.googleapis.com cdnjs.cloudflare.com native.testing.equest.com www.youtube.com demo.docusign.net youtu.be player.vimeo.com docs.google.com 'unsafe-inline' 'unsafe-eval' data: font;frame-src 'self' *.amazonaws.com native.testing.equest.com sandbox.e-signlive.com;connect-src 'self' *.orangehrm.com;img-src * 'self' data: blob:
Public-Key-Pins: pin-sha256="blgmjf3Tb3C0sUqb7jo4axiZAnr327fX0ycrUGqjw2k=";pin-sha256="yQhO6YqQX5Y/NxyHAjXnI3jOtYWUm/TtRr666RunXRg="; pin-sha256="puCdyuZdXoDc5jSd
Response in test:
{
server: 'nginx',
date: 'Thu, 27 Jun 2024 05:16:30 GMT',
'content-type': 'text/html; charset=UTF-8',
'transfer-encoding': 'chunked',
connection: 'close',
'cache-control': 'no-cache, private',
'x-content-type-options': 'nosniff',
'x-xss-protection': '1; mode=block',
'strict-transport-security': 'max-age=63072000; includeSubdomains;',
'content-security-policy': "default-src blob: 'self' *.projects-abroad.net fonts.googleapis.com www.google.com fonts.gstatic.com code.jquery.com maxcdn.bootstrapcdn.com ajax.googleapis.com cdnjs.cloudflare.com native.testing.equest.com www.youtube.com demo.docusign.net youtu.be player.vimeo.com docs.google.com 'unsafe-inline' 'unsafe-eval' data: font;frame-src 'self' *.amazonaws.com native.testing.equest.com sandbox.e-signlive.com;connect-src 'self' *.orangehrm.com;img-src * 'self' data: blob:",
'public-key-pins': 'pin-sha256="blgmjf3Tb3C0sUqb7jo4axiZAnr327fX0ycrUGqjw2k=";pin-sha256="yQhO6YqQX5Y/NxyHAjXnI3jOtYWUm/TtRr666RunXRg="; pin-sha256="puCdyuZdXoDc5jSdcGKU6mdjd0VNq16yoaO2BcDF36A="; max-age=63072000; includeSubDomains'
}

Expected behavior

Ideally would need to display location kv pair in the response.headers() or response.headerArrays()

Actual behavior

Location kv pair is missing in respnse headers

Additional context

No response

Environment

System:
  OS: Windows 11
  CPU: (8) arm64
Binaries:
  npm: 10.2.4 
npmPackages:
  @playwright/test: 1.45.0

[gokulsam07]

Didn't check the url method, not an issue