benklop / microblog-purple

Automatically exported from code.google.com/p/microblog-purple
GNU General Public License v3.0
0 stars 0 forks source link

Identi.ca doesn't work with the proxys in our company #173

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

1. Create and Identi.ca account and connect 
2. it seems to connect, but doesn't, as new dents from friends are not
displayed

Debug log from Pidgin attached.

What version of the product are you using? On what operating system?

$ rpm -q pidgin purple-microblog
pidgin-2.6.5-1.fc12.x86_64
purple-microblog-0.2.4-3.fc12.x86_64
$ uname -r
2.6.32.4-28.fc12.x86_64
$ cat /etc/fedora-release 
Fedora release 12 (Constantine)

Please provide any additional information below.

microblog-purple works great on my machines at home. But here at work we
have a transparent proxy which afaics is part of the problem.

Original issue reported on code.google.com by thorsten...@gmail.com on 22 Jan 2010 at 10:07

Attachments:

GoogleCodeExporter commented 9 years ago
We have a second, older proxy here at work which doesn't work any better. See
attached log for details.

Original comment by thorsten...@gmail.com on 22 Jan 2010 at 10:12

Attachments:

GoogleCodeExporter commented 9 years ago
Forgot to mention: connecting to twitter works fine with the transparent proxy.

Original comment by thorsten...@gmail.com on 22 Jan 2010 at 10:13

GoogleCodeExporter commented 9 years ago
What's the result when you try to open
http://identi.ca/api/statuses/friends_timeline.xml ?

Also, are you connect to twitter via http or https?

Original comment by somsaks on 22 Jan 2010 at 1:12

GoogleCodeExporter commented 9 years ago
thx for looking into this

> What's the result when you try to open
> http://identi.ca/api/statuses/friends_timeline.xml ?

Tried it with Firefox and it works just fine with both the transparent proxy 
and the
one I have to configure manually.

> Also, are you connect to twitter via http or https?

https

Original comment by thorsten...@gmail.com on 25 Jan 2010 at 7:24

GoogleCodeExporter commented 9 years ago
Have you try uncheck "Use HTTPS", or using firefox to open 
https://identi.ca/api instead?

Original comment by somsaks on 25 Jan 2010 at 8:04

GoogleCodeExporter commented 9 years ago
> Have you try uncheck "Use HTTPS",

There is no such checkbox in the preferences for identi.ca accounts afaics 
(Might be
related to Issue 171). But there is one for twitter accounts: I tried to 
uncheck it
at it still worked.

> or using firefox to open https://identi.ca/api instead?

Sorry, can't follow. When I browse there using firefox I just get an error 
message
saying "Unbekannter Benutzer" (which likely is "Unkown User" in English). 
Doesn't
matter if I'm logged in or now using firefox earlier.

Original comment by thorsten...@gmail.com on 25 Jan 2010 at 9:11

GoogleCodeExporter commented 9 years ago
I used wireshark to trace the conversation. pidgin-microblog does not use fully 
qualified URLs causing 400 BAD REQUEST from the proxy.

GET /api/account/verify_credentials.xml HTTP/1.1
Authorization: Basic XXXXXXXXXXXXXXXXXXXXXXXXXXX==
Host: identi.ca
User-Agent:curl/7.18.0 (i486-pc-linux-gnu) libcurl/7.18.0 OpenSSL/0.9.8g 
zlib/1.2.3.3 libidn/1.1
Accept: */*
X-Twitter-Client: mbpidgin
X-Twitter-Client-Version: 0.1
X-Twitter-Client-Url: http://microblog-purple.googlecode.com/files/mb-0.1.xml
Connection: Close
Pragma: no-cache

I think the get request should start with

GET http://identi.ca//api/account/verify_credentials.xml HTTP/1.1

instead.

Original comment by jan.ditt...@gmail.com on 27 Jan 2011 at 12:18

GoogleCodeExporter commented 9 years ago
the attached patch changes mb_http.c to use the full URL instead of the URL 
path only and should fix the broken proxy behaviour.

Original comment by jan.ditt...@gmail.com on 5 Feb 2011 at 8:43

Attachments:

GoogleCodeExporter commented 9 years ago
Patch merged with SVN, with some modification. I use MAXHOSTNAMELEN instead of 
"strlen("unknown")".

Original comment by somsaks on 7 Feb 2011 at 9:38

GoogleCodeExporter commented 9 years ago
Thanks for applying the patch. I missed the hostname in my patch and only 
included protocol specification ... thats were these "mysterial" extra bytes in 
my calculation came from.

Original comment by jan.ditt...@gmail.com on 7 Feb 2011 at 11:52

GoogleCodeExporter commented 9 years ago
Tried the patch attached, tried the patch that was committed to svn and tried 
the svn snapshot from a few minutes ago: None of those solutions improved the 
solution for me: identi.ca still does not work :-/

Is there a way to reopen this bug?

Original comment by thorsten...@gmail.com on 8 Feb 2011 at 7:35

GoogleCodeExporter commented 9 years ago

Original comment by andresen.nils@gmail.com on 8 Feb 2011 at 8:19

GoogleCodeExporter commented 9 years ago
Could you (Poster of Comment #11) try to capture and post the HTTP stream for 
debugging purposes?

Original comment by jan.ditt...@gmail.com on 8 Feb 2011 at 10:20

GoogleCodeExporter commented 9 years ago
Hi, 
the modifications break build in cygwin/mingw.
mingw has no MAXHOSTNAMELEN.
I found some places in the net which state define MAXHOSTNAMELEN 64 for mingw...
So the attached patch fixes the compile-error. I do not know whether it is a 
"good" solution, though.

Original comment by andresen.nils@gmail.com on 3 May 2011 at 1:42

Attachments:

GoogleCodeExporter commented 9 years ago
I included the patch from comment#14 in svn today.
Thorsten (sender of comment#11) - does the problem still persist or can we 
re-close this issue? 

Original comment by andresen.nils@gmail.com on 15 Jun 2011 at 8:40

GoogleCodeExporter commented 9 years ago
> I included the patch from comment#14 in svn today.
> Thorsten (sender of comment#11) - does the problem still persist or can we 
re-close this issue? 

Build the svn version, still does not work for me :-/

I really need to sit down and capture the http stream, but I need to find time 
for it; maybe I need to come to the office on the weekend :-/

Original comment by thorsten...@gmail.com on 15 Jun 2011 at 8:59

GoogleCodeExporter commented 9 years ago
Thorsten,
sorry to hear this. Hope you find the time.

Original comment by andresen.nils@gmail.com on 15 Jun 2011 at 11:41