error 417

Message boards : Questions and problems : error 417
Message board moderation

To post messages, you must log in.

AuthorMessage
USTL-FIL (Lille Fr)

Send message
Joined: 3 Jun 13
Posts: 12
France
Message 49493 - Posted: 3 Jun 2013, 15:27:31 UTC

Hi all,

Wy the old and boring http error 417 alway still here in the new version of boinc?
it's not possible to automaticaly include the <options><http_1_0>1</http_1_0></options> in cc_config when proxy is enable?
Thanks!
Mike
ID: 49493 · Report as offensive
USTL-FIL (Lille Fr)

Send message
Joined: 3 Jun 13
Posts: 12
France
Message 50343 - Posted: 28 Aug 2013, 15:03:12 UTC - in response to Message 49493.  

nobody?
ID: 50343 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 50344 - Posted: 28 Aug 2013, 15:47:33 UTC - in response to Message 50343.  
Last modified: 28 Aug 2013, 15:53:41 UTC

No. BOINC will not automatically change to an older HTTP version when a proxy is used.
Also, since the installing user has to set up BOINC with a proxy capability, one would think that that user is knowledgeable enough to change this, and if not, that he asks for help on how to do so.
ID: 50344 · Report as offensive
USTL-FIL (Lille Fr)

Send message
Joined: 3 Jun 13
Posts: 12
France
Message 50387 - Posted: 2 Sep 2013, 14:38:40 UTC - in response to Message 50344.  

No. BOINC will not automatically change to an older HTTP version when a proxy is used.
Also, since the installing user has to set up BOINC with a proxy capability, one would think that that user is knowledgeable enough to change this, and if not, that he asks for help on how to do so.


Thank you for your reply!
Ok, but in this case, why not adding a checkbox in boincmanager whith the proxy parameters for enable http_1_0?
Not everyone know internal boinc xml syntax!
Mickaƫl

ID: 50387 · Report as offensive

Message boards : Questions and problems : error 417

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.