Bug 215777

Summary: Configuration to use HTTP instead of HTTPS
Product: [Applications] digikam Reporter: Wickersheimer Jeremy <jwickers>
Component: Plugin-WebService-FacebookAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED INTENTIONAL    
Severity: wishlist CC: caulier.gilles, dirk.kde
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Unspecified   
Latest Commit: Version Fixed/Implemented In: 2.0.0
Sentry Crash Report:

Description Wickersheimer Jeremy 2009-11-23 04:21:03 UTC 
Version:            (using KDE 4.3.3)
Installed from:    Gentoo Packages

Because there is a problem currently with KDE using proxy to connect to SSL sites (see Bug 177432) i wished there was a checkbox / option to have the export / import to use non SSL connections.

I am posting for the Facebook but this may apply to other export/import plugins.

The reason for this: in some countries (ie: China) access to Facebook (and other social services) is blocked, therefore one has to use a proxy to access them.

Locally i simply patched the code and replaced the URL strings to use HTTP, and it works fine for me. The only issue i had was that in order to allow the plugin to work with facebook, one first has to login and allow the application. Even with an HTTP link the form would post in HTTPS.
A simple workaround is to use another browser to do this part (opera / firefox / arora / ...).

Later the import / export works from digikam (for example) just using HTTP.
Comment 1 Dirk Tilger 2011-06-23 09:19:51 UTC 
The legacy authentication that worked with HTTP has been depreciated. OAuth2, the authentication method for digikam 2.0.0 KIPI plugins requires HTTPS.