jfrederickson / pidgin-sendscreenshot

Automatically exported from code.google.com/p/pidgin-sendscreenshot
GNU General Public License v2.0
0 stars 0 forks source link

Can't connect to HTML upload hosts when using proxy server. #4

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Select any HTML upload host.
2. Send screenshot to anyone using HTML upload
3. Failure

What is the expected output? What do you see instead?
Expected - File uploaded to HTML host.
Result - "couldn't connect to host" error.

What version of the plugin are you using? On what operating system?
0.81, Winxp SP3

Please provide any additional information below.

Original issue reported on code.google.com by duane.br...@gmail.com on 14 May 2010 at 1:43

GoogleCodeExporter commented 9 years ago
Hello,

Some proxy servers are configured to block "POST" requests.
Internally, the plugin fills an HTML form for you and send it to the selected 
image
hosting provider through the "POST" method... so that's probably why it doesn't 
work.

But there's an easy way to see whether this issue is caused by the plugin or 
not.
When connected to a proxy server, please go to one of the upload host (say
http://imageshack.us/) and try to upload a picture.
If the upload is successful, then the issue comes from the plugin.

Original comment by these.rberger@gmail.com on 15 May 2010 at 2:27

GoogleCodeExporter commented 9 years ago
Sorry, I was too brief in my initial problem description.  I did test several 
hosts
prior to reporting this, and just re-verified the issue again.

When working through the web interface of http://imageshack.us, the upload of an
image is successful.

When using the Pidgin plugin, the upload to imageshack fails and the following 
error
appears:  
              Error
              Failed to upload the screenshot to 'ImageShack'!
              connect() timed out!

Original comment by duane.br...@gmail.com on 28 May 2010 at 7:12

GoogleCodeExporter commented 9 years ago
Thanks for testing, so this issue apparently comes from the plugin...

I now need technical details on how the proxy is configured and I think those
informations should be kept private. Please e-mail me.

Original comment by these.rberger@gmail.com on 4 Jun 2010 at 4:00

GoogleCodeExporter commented 9 years ago

Original comment by these.rberger@gmail.com on 7 Aug 2010 at 3:28

GoogleCodeExporter commented 9 years ago
If you're using libcurl in the plugin, you should pass in the proxy connection 
settings to it.  You can pull these details from libpurple using the 
purple_global_proxy_get_info(), purple_proxy_info_get_*() functions

Original comment by eionrobb on 12 Apr 2011 at 5:46