Problem accessing cloud behind a proxy

[Dirk Hohndel]

Hi Davide,

> On Nov 2, 2017, at 1:36 AM, Davide DB <dbdavide at gmail.com> wrote:
> 
> 
> File locations:
> 
> cloud URL set as "https://cloud.subsurface-divelog.org//git/dbdavide@gmail.com[dbdavide@gmail.com] <https://cloud.subsurface-divelog.org//git/dbdavide@gmail.com[dbdavide@gmail.com]>"
> Local git storage: C:\Users\someuser\AppData\Roaming\Subsurface/cloudstorage/29fc20f013e9f1fb
> Cloud URL: https://cloud.subsurface-divelog.org//git/dbdavide@gmail.com[dbdavide@gmail.com] <https://cloud.subsurface-divelog.org//git/dbdavide@gmail.com[dbdavide@gmail.com]>
> Image hashes: C:\Users\someuser\AppData\Roaming\Subsurface/hashes
> Local picture directory: C:\Users\someuser\AppData\Roaming\Subsurface/picturedata/
> 
> build with Qt Version 5.9.1, runtime from Qt Version 5.9.1
> subsurface.facebook: Current url call QUrl("https://www.facebook.com/login.php?skip_api_login=1&api_key=427722490709000&signed_next=1&next=https%3A%2F%2Fwww.facebook.com%2Fv2.5%2Fdialog%2Fo <https://www.facebook.com/login.php?skip_api_login=1&api_key=427722490709000&signed_next=1&next=https%3A%2F%2Fwww.facebook.com%2Fv2.5%2Fdialog%2Fo>
> F%2Fwww.facebook.com <http://2fwww.facebook.com/>%2Fconnect%2Flogin_success.html%3Ferror%3Daccess_denied%26error_code%3D200%26error_description%3DPermissions%2Berror%26error_reason%3Duser_denied%23_%3D_&display=popup&l
> subsurface.facebook: Response without access token!
> QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.
> QNetworkAccessCache::addEntry: overriding active cache entry 'auth:proxy-http://someuser@proxy.domain.it:8080 <http://someuser@proxy.domain.it:8080/>'
> QNetworkAccessCache::addEntry: overriding active cache entry 'auth:proxy-http://proxydomain.domain.it:8080 <http://proxydomain.domain.it:8080/>'
> QNetworkAccessCache::addEntry: overriding active cache entry 'auth:proxy-http://someuser@proxydomain.domain.it:8080 <http://someuser@proxydomain.domain.it:8080/>'
> QNetworkAccessCache::addEntry: overriding active cache entry 'auth:proxy-http://proxydomain.domain.it:8080 <http://proxydomain.domain.it:8080/>'
> QNetworkAccessCache::addEntry: overriding active cache entry 'auth:proxy-http://someuser@proxydomain.domain.it:8080 <http://someuser@proxydomain.domain.it:8080/>'
> QNetworkAccessCache::addEntry: overriding active cache entry 'auth:proxy-http://proxydomain.domain.it:8080 <http://proxydomain.domain.it:8080/>'
> QNetworkAccessCache::addEntry: overriding active cache entry 'auth:proxy-http://someuser@proxydomain.domain.it:8080 <http://someuser@proxydomain.domain.it:8080/>'
> QNetworkAccessCache::addEntry: overriding active cache entry 'auth:proxy-http://proxydomain.domain.it:8080 <http://proxydomain.domain.it:8080/>'
> QNetworkAccessCache::addEntry: overriding active cache entry 'auth:proxy-http://someuser@proxydomain.domain.it:8080 <http://someuser@proxydomain.domain.it:8080/>'
> QNetworkAccessCache::addEntry: overriding active cache entry 'auth:proxy-http://proxydomain.domain.it:8080' <http://proxydomain.domain.it:8080'>
> 
> When I manually access cloud via UI I get:

What exactly does that mean? Do you mean you are clicking on File->Open cloud storage (Apri memoria cloud)? 

> cloud URL set as "https://cloud.subsurface-divelog.org//git/dbdavide@gmail.com[dbdavide@gmail.com] <https://cloud.subsurface-divelog.org//git/dbdavide@gmail.com[dbdavide@gmail.com]>"
> Opening cloud storage from: "https://cloud.subsurface-divelog.org//git/dbdavide@gmail.com[dbdavide@gmail.com] <https://cloud.subsurface-divelog.org//git/dbdavide@gmail.com[dbdavide@gmail.com]>"
> Set the current dive site: 0
> git storage: Synchronising data file
> git storage: create_local_repo
> Cloud storage: checking connection to cloud server
> Checking cloud connection...
> git storage: Waiting for cloud connection (1 second(s) passed)
> git storage: Waiting for cloud connection (2 second(s) passed)
> git storage: Waiting for cloud connection (3 second(s) passed)
> set proxy to "http://someuser:SomePassword@proxydomain.domain.it:8080 <http://someuser:SomePassword@proxydomain.domain.it:8080/>"
> error message was Failed to set proxy: Parametro non corretto.

OK, so I never tested having a password encoded in the proxy URL.
I'm guessing that we don't unpack that correctly. This gives me more code to stare at.

/D
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20171102/07d9a76d/attachment.html>