Cypress does not bypass a domain properly

[catalin7mar]

Hi!
I work in an organization that uses PAC. From the cypress specifications I have to use:

If your organization uses a PAC file, contact a network administrator to ask what HTTP proxy you should be using to access the general Internet, then use that proxy with Cypress.

However, I can't use a proxy for my project, because "internal" calls should be called just without a proxy. The portal works only in the intranet and without proxy.

This is the response from the support team (from my organization):

Please clarify with cypress team, if no PAC can be used, then tool must be adjusted so that no proxy is used because "internal" calls should be called just without a proxy.

So I used NO_PROXY, like in the Cypress documentation says and the domain from my project is bypassed (at least it says in Cypress Settings)

"test:no_proxy1": "set NO_PROXY=int....at.inside && npm run test:open",

However, if I try to run a test case I get this error:

From this, I understand that Cypress doesn't actually bypass the domain that is set.

[flotwig]

@catalin7mar There appears to be a space in your Proxy Bypass List:

int.....at.inside , 127.0.0.1

There should not be a space after inside.

I don't think this is coming from Cypress, since the code for this doesn't insert a space:

cypress/packages/server/lib/util/proxy.ts

Lines 44 to 49 in 16a4203

	if (!noProxyParts.includes('<-loopback>')) {
	debug('<-loopback> not found, adding localhost to NO_PROXY')
	process.env.NO_PROXY = noProxyParts.concat([
	'127.0.0.1', '::1', 'localhost',
	]).join(',')
	}

Can you try another means of setting NO_PROXY to get rid of that space? I'm fond of cross-env on Windows:

npm i -g cross-env
cross-env NO_PROXY=int.....at.inside npm run test:open

---

Potentially we should add some filtering/automatic trimming of the NO_PROXY, HTTP_PROXY, and HTTPS_PROXY variables, since this seems to happen regularly.

[catalin7mar]

Hi! Thanks a lot! I added a new random domain after int.....at.inside and now only the second has space - but I don't care, I just need to bypass the first one properly.

"test:no_proxy1": "set NO_PROXY=int....at.inside, apple && npm run test:open",

[AlexisNo]

Hi, I had a similar problem with a GitLab runner and the application to test inside an intranet.

I managed to get it working specifying the full domain: abc.example.internal instead of example.internal. The latest works correctly for tools like wget, but I had to add the first one to the list to make it work with Cypress: abc.example.internal,example.internal. (I still needed example.internalother subdomains to continue to be reached by other tools like wget)

I'm not sure if the behavior should be changed as no_proxy seems to be more a convention than a standard. Maybe the documentation should be more explicit about this.

[AlexisNo]

NO_PROXY=*.example.internal works correctly too.

[hanatharesh2712]

I tried with NO_PROXY=*.example.internal

but, it doesn't show the Bypass proxy list as per NO_PROXY.

any other workaround to fix this?