vkotakte-ru-plugin bzr945 fails to add vkontakte account when $http_proxy enabled

[Stanislav Hanzhin]

When proxy is enabled it can't load vkontakte.ru Authentication page.

When we're not behind a proxy, we get the following.

Maybe I've missed something.

N.B. Paths in traceback are shortened for security reasons. they are relative to users' home dir.
Traceback (most recent call last):
  File "vkontakte-ru-plugin/gwibber/microblog/plugins/vkontakte/gtk/vkontakte/__init__.py", line 109, in on_vk_auth_title_change
    app_id=VK_APP_ID).getProfiles(uids=data["mid"], fields="first_name,last_name")
  File "vkontakte-ru-plugin/gwibber/microblog/plugins/vkontakte/vk_api_wrapper.py", line 86, in __call__
    return self._load(method, **kwargs)
  File "vkontakte-ru-plugin/gwibber/microblog/plugins/vkontakte/vk_api_wrapper.py", line 67, in _load
    if res.has_key("error"):
AttributeError: 'NoneType' object has no attribute 'has_key'

[Stanislav Hanzhin (hanzhin-stas)]

When gnome proxy is enabled, gwibber uses proxy till user logout. After relogin gwibber starts with clean proxy settings and account is successfully added. When proxy is disabled after it was enabled, the following occurs: authentication page displays and after successful login we get Login Success message and nothing happened because plugin can't contact API to determine user's info.

[Sergey Prokhorov (seriy-pr)]

Main problem is that vk API auth/session token strongly depends on the IP adress. When IP adress changes, token stop work.

Second problem - Gwibber use py-webkit for display auth pages and pycurl for contact with API. But pywebkit doesn't support http_proxy environment since it been moved from libcurl to libsoup https://bugs.launchpad.net/ubuntu/+source/pywebkitgtk/+bug/424833

So, we need to wait fixes on pywebkit (see bug #424833 for details)

[Sergey Prokhorov (seriy-pr)]

Hey, I found that this problem is affects Gwibber globally, not only VK plugin: Gwibber bug #259830