Support Basic Authentication on Content-Type: text/plain pages

[mrtc0]

Purpose

Fix issue Basic Authentication fails on pages with Content-Type: text/plain.
As a use case, if a proxy in front of the application is responsible for Basic Authentication, proxy may return a text/plain response.

Approach

Even on a page with Content-Type: text/plain, the _tryAuthorizeWithHttpBasicAuthCredentials function will be called to authorize Basic Authentication.

References

N/A

Pre-Merge TODO

• Write tests for your proposed changes
• Make sure that existing tests do not fail

[AlexKamaev]

At present, TestCafe cannot open text pages in Native Automation mode: #7786
Why do you need to open a text page in Native Automation mode? Please describe your usage scenario in detail.

[mrtc0]

@AlexKamaev The test target page is served with Content-Type: text/html, but there might be cases where the response for the initial challenge of Basic authentication returns with Content-Type: text/plain.

In my case, the Basic authentication component implemented using Go's net/http was returning a first challenge's response with Content-Type: text/plain and a status code of 401.
This can be fixed by modifying the response to return with Content-Type: text/html, However, there might be situations where such modifications are not always controllable or feasible due to various constraints or limitations in the environment or the system.

[AlexKamaev]

In this case, the described issue is the same as #7786. We need to support injecting TestCafe scripts in the test page. You can try modifying the ContentType response header as you mentioned.

Please also remove the duplicated code:

const contentType = responseHeaders
?.find(header => header.name.toLowerCase() === 'content-type')
?.value;

Moreover, I think it will be enough to write a test for a text page without HttpAuth.

[AlexKamaev]

I've closed this PR since there was no activity for a long time