How can I configure Vite's proxy to work behind a corporate proxy?

It looks like the issue isn’t in your Vite proxy configuration (which works correctly on your private computer) but rather in how your company machine is handling external requests. Since CURL also fails on that PC, the problem is that the machine needs to go through your company proxy to reach https://www.lorem.com.

Here are a few steps you can try:

1. Use Environment Variables for the Proxy:
   Node’s built‐in HTTP/HTTPS modules (and many libraries) look for the proxy settings in the environment rather than using npm’s configuration. Try setting the following environment variables before running Vite:

   BASHCopied
   export HTTP_PROXY=http://myproxy.xyz:123
   export HTTPS_PROXY=http://myproxy.xyz:123
   npm run dev

   On Windows you can set them like:

   CMDCopied
   set HTTP_PROXY=http://myproxy.xyz:123
   set HTTPS_PROXY=http://myproxy.xyz:123
   npm run dev

2. Check if the Proxy Requires Authentication:
   If your company proxy requires credentials, make sure to include them in the URL:

   BASHCopied
   export HTTP_PROXY=http://username:password@myproxy.xyz:123
   export HTTPS_PROXY=http://username:password@myproxy.xyz:123
   npm run dev

3. Verify Network Access Outside Vite:
   Since CURL isn’t working either, confirm that the company’s network settings indeed require a proxy for external requests. You might need to consult with your network administrator for the proper proxy settings.

4. Consider a Custom Proxy Agent (if needed):
   If setting environment variables does not work (or if Vite’s internal proxy doesn’t pick them up), you may have to use a custom agent (for example, using the “global-agent” npm package) to force Node’s HTTP/HTTPS modules to use your proxy. This would require additional configuration and might look like:

   JAVASCRIPTCopied
   // install global-agent
   // npm install global-agent
   const { bootstrap } = require('global-agent');
   bootstrap();
   
   // Now your HTTP/HTTPS requests should use process.env.HTTP_PROXY / HTTPS_PROXY

   Then run your app with the proper environment variables set.

By ensuring that Node is picking up your company’s proxy settings via environment variables, your Vite dev server should be able to fetch the external CSS file even from behind a corporate proxy.