dig dug is not connecting with sauce labs correctly when behind http proxy with authentication about digdug HOT 8 CLOSED

Thanks for your report! An upstream ticket will be opened to add CONNECT tunnelling through a proxy, but we won’t be changing any dependencies.

from digdug.

Hi @csnover, can you let me know if the upstream ticket you mentioned has been added outwith https://bugs.dojotoolkit.org/ticket/18424 ?

I'd like to get some traction on this, whilst the hacking on that ticket worked at home with privoxy, it didn't in my workplace, I'm willing to do more testing/hacking if needed so let me know. I've also pinged @bryanforbes about this

from digdug.

Can you explain what's wrong with changing dependencies - why invent a wheel when it's already done?

from digdug.

@bartoszkaczorek because we'd rather fix issues with upstream dependencies when possible rather than swapping out an upstream dependency every time there's an issue. There are a number of features in dojo/request that we use for mocking requests, etc., and it wouldn't be very friendly to our users to break those existing patterns. You could argue that anything is a reinvention of something else (e.g. the request library you've linked to isn't the first ever library to solve requests, etc.). :)

from digdug.

@bartoszkaczorek In addition to what @dylans said, the request library you’re mentioning introduces other dependencies (= slower install), doesn’t follow our standards and conventions (e.g. using Promises for asynchronous operations), and so would require us to rewrite all the networking code in Dig Dug. It’s not a 1:1 replacement. So there are both philosophical and practical reasons why it’s not possible to simply swap it.

from digdug.

For anyone looking for a workaround for this issue: https://www.npmjs.com/package/digdug-null-sauce-labs-tunnel

from digdug.

I have started adding more robust proxy configuration to Dojo as part of dojo/core#335.

from digdug.

Closing this since Intern and digdug no long use dojo for requests. There is a potentially related issue at theintern/intern#1065 if this still happens with current Intern.

from digdug.