Jim Speir

As someone who doesn't write right to left, it's hard for me to visualise how this would work so I googled some arabic bill memes. There's actually a couple but...

Supposedly (according to superagent's docs at https://visionmedia.github.io/superagent/, look for "Forcing specific connection IP address") it should be possible to use: ``` request("domain.com") .get("/") .connect("127.0.0.1") ... ``` However, I tried this...

A workaround, though not using supertest, is to use superagent directly: ``` var mocha = require('mocha'); var forEach = require('mocha-each'); var assert = require("assert"); var superagent = require('superagent') var ports...

Still seeing this issue on my end btw. My logs to add to this: ``` (SONOS)SSLSessionFactory: SSL engine initialized (SONOS)WSResponse: bad request (403) (SONOS)DoCall: parse xml failed (SONOS)GetAppLink: parse xml...

You could ansible them otherwise you'd need to set that registry key as part of the image. I'd suggest ansible and just add a startup script to run it each...

I've added my environmental information above because I know they work in my case although I can hardly say I'm using all the features of it. My intention is to...

Would it be worthwhile simply adding a list of working configurations and some notes somewhere? I'd be happy to go into more detail on my setup.

Thanks @apatard , I've added an issue there to see what their feelings are. Seems I'm the only one to ask about it. Assuming it's okay I suspect I may...

Nah nothing on my end dude 🤷

My work are dragging their heels on approving me working to fix this issue but I'm hoping that I'm able to do so. It will have major pros for us...