[Digidoc client] Signing documents fails when inside a network that uses proxy with authentication

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Be connected to a network that connects to Internet through a proxy that 
needs authentication
2. Try to use Digidoc to sign any document
3. -

What is the expected output? What do you see instead?
I expect to see "Document signed" but I get "Check internet connection". 

What version of the product are you using? On what operating system?
Digidoc3, Windows XP SP3. Proxy server: Bluecoat.

Please provide any additional information below.
For testing, I connected to public internet and tested signing from there, it 
worked. From company network it didn't work. You're welcome to ask any 
additional questions.

Original issue reported on code.google.com by MarioMar...@gmail.com on 13 Oct 2010 at 9:29

[GoogleCodeExporter]

Additional information: I tried with two different proxy server addresses, 
which both have been tested and are working with browsers. Other fields: port 
and credentials are filled in and checked multiple times. 

Original comment by MarioMar...@gmail.com on 13 Oct 2010 at 10:12

[GoogleCodeExporter]

Thanks for the report, Mario. Does anything change if you try to sign a bdoc 
container instead of ddoc?

In any case, for anyone who starts looking into this, openssl 1.0 has support 
for custom OCSP headers: http://rt.openssl.org/Ticket/Display.html?id=2064

Original comment by kalevlember@gmail.com on 13 Oct 2010 at 12:36

[GoogleCodeExporter]

Can confirm this under linux.

Original comment by andres.k...@gmail.com on 23 Oct 2010 at 3:54

[GoogleCodeExporter]

Tried bdoc also, same issue. 

Original comment by MarioMar...@gmail.com on 30 Nov 2010 at 7:09