Menu
▾
▴
htmlunit-develop
|
From: SourceForge.net <no...@so...> - 2003-07-18 10:59:43
|
Feature Requests item #773552, was opened at 2003-07-18 11:59 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=448269&aid=773552&group_id=47038 Category: None Group: None Status: Open Priority: 5 Submitted By: Robert Wittams (rjwittams) Assigned to: Nobody/Anonymous (nobody) Summary: Support proxy better - use http client more Initial Comment: Use http clients abilities more. The proxy server and credential apis are too simple. Eg NTLM auth, etc. Why not expose the HttpClient credential api? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=448269&aid=773552&group_id=47038 |
|
From: SourceForge.net <no...@so...> - 2003-07-18 19:52:49
|
Feature Requests item #773552, was opened at 2003-07-18 06:59 Message generated for change (Comment added) made by mbowler You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=448269&aid=773552&group_id=47038 Category: None Group: None Status: Open Priority: 5 Submitted By: Robert Wittams (rjwittams) Assigned to: Nobody/Anonymous (nobody) Summary: Support proxy better - use http client more Initial Comment: Use http clients abilities more. The proxy server and credential apis are too simple. Eg NTLM auth, etc. Why not expose the HttpClient credential api? ---------------------------------------------------------------------- >Comment By: Mike Bowler (mbowler) Date: 2003-07-18 15:52 Message: Logged In: YES user_id=46756 The original plan was to completely isolate commons-httpclient so that it could be replaced if needed. At the time, it was not being actively maintained so this seemed a reasonable precaution. Today commons-httpclient is being very actively maintained so this decision doesn't make as much sense as it used to. Exposing the api isn't quite as simple as it sounds as there isn't a one-to-one mapping of WebClient to HttpClient. This was due to weaknesses in the httpclient api at the time the WebConnection was initially written. I believe that this could be changed today but it would require pretty much a rewrite of HttpWebConnection. I'll have to give this some thought. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=448269&aid=773552&group_id=47038 |
|
From: SourceForge.net <no...@so...> - 2003-07-18 20:22:34
|
Feature Requests item #773552, was opened at 2003-07-18 10:59 Message generated for change (Comment added) made by csell You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=448269&aid=773552&group_id=47038 Category: None Group: None Status: Open Priority: 5 Submitted By: Robert Wittams (rjwittams) Assigned to: Nobody/Anonymous (nobody) Summary: Support proxy better - use http client more Initial Comment: Use http clients abilities more. The proxy server and credential apis are too simple. Eg NTLM auth, etc. Why not expose the HttpClient credential api? ---------------------------------------------------------------------- Comment By: Christian Sell (csell) Date: 2003-07-18 20:15 Message: Logged In: YES user_id=105319 a little comment: I have recently used HttpWebconnction to adapt HtmlUnit to another web client API (a descendant of W3Cs Jigsaw). I found this a rather easy process, despite the warnings about the "internal" character of HttpWebconnction. I would appreciate if this interface would remained intact - and maybe promoted to official status. HttpClient does have shortcomings, IMO. Christian ---------------------------------------------------------------------- Comment By: Mike Bowler (mbowler) Date: 2003-07-18 19:52 Message: Logged In: YES user_id=46756 The original plan was to completely isolate commons-httpclient so that it could be replaced if needed. At the time, it was not being actively maintained so this seemed a reasonable precaution. Today commons-httpclient is being very actively maintained so this decision doesn't make as much sense as it used to. Exposing the api isn't quite as simple as it sounds as there isn't a one-to-one mapping of WebClient to HttpClient. This was due to weaknesses in the httpclient api at the time the WebConnection was initially written. I believe that this could be changed today but it would require pretty much a rewrite of HttpWebConnection. I'll have to give this some thought. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=448269&aid=773552&group_id=47038 |
|
From: SourceForge.net <no...@so...> - 2003-07-18 21:55:40
|
Feature Requests item #773552, was opened at 2003-07-18 11:59 Message generated for change (Comment added) made by rjwittams You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=448269&aid=773552&group_id=47038 Category: None Group: None Status: Open Priority: 5 Submitted By: Robert Wittams (rjwittams) Assigned to: Nobody/Anonymous (nobody) Summary: Support proxy better - use http client more Initial Comment: Use http clients abilities more. The proxy server and credential apis are too simple. Eg NTLM auth, etc. Why not expose the HttpClient credential api? ---------------------------------------------------------------------- >Comment By: Robert Wittams (rjwittams) Date: 2003-07-18 22:38 Message: Logged In: YES user_id=270100 Surely the least ugly way to do this is to give WebClient a constructor taking an implementation of WebConnection. The setWebConnection is a pretty ugly way to do it imo... And deprecate the proxy settings constructor. Its misleading as it implies thats all the proxy settings you'll ever need. The cred stuff should just go. It either needs expanding to cover all the auth methods, which just duplicates HttpClient, or removal... I vote number 2. That kind of stuff is in my mind closely tied to the WebConnection, should be all part and parcel of that.. ---------------------------------------------------------------------- Comment By: Christian Sell (csell) Date: 2003-07-18 21:15 Message: Logged In: YES user_id=105319 a little comment: I have recently used HttpWebconnction to adapt HtmlUnit to another web client API (a descendant of W3Cs Jigsaw). I found this a rather easy process, despite the warnings about the "internal" character of HttpWebconnction. I would appreciate if this interface would remained intact - and maybe promoted to official status. HttpClient does have shortcomings, IMO. Christian ---------------------------------------------------------------------- Comment By: Mike Bowler (mbowler) Date: 2003-07-18 20:52 Message: Logged In: YES user_id=46756 The original plan was to completely isolate commons-httpclient so that it could be replaced if needed. At the time, it was not being actively maintained so this seemed a reasonable precaution. Today commons-httpclient is being very actively maintained so this decision doesn't make as much sense as it used to. Exposing the api isn't quite as simple as it sounds as there isn't a one-to-one mapping of WebClient to HttpClient. This was due to weaknesses in the httpclient api at the time the WebConnection was initially written. I believe that this could be changed today but it would require pretty much a rewrite of HttpWebConnection. I'll have to give this some thought. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=448269&aid=773552&group_id=47038 |
|
From: SourceForge.net <no...@so...> - 2005-05-10 07:14:05
|
Feature Requests item #773552, was opened at 2003-07-18 06:59 Message generated for change (Comment added) made by sdanig You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=448269&aid=773552&group_id=47038 Category: None Group: None Status: Open Priority: 5 Submitted By: Robert Wittams (rjwittams) Assigned to: Nobody/Anonymous (nobody) Summary: Support proxy better - use http client more Initial Comment: Use http clients abilities more. The proxy server and credential apis are too simple. Eg NTLM auth, etc. Why not expose the HttpClient credential api? ---------------------------------------------------------------------- Comment By: Daniel Gredler (sdanig) Date: 2005-05-10 03:14 Message: Logged In: YES user_id=1109422 This feature request can probably be closed, as the feature has been implemented. http://htmlunit.sourceforge.net/apidocs/com/gargoylesoftware/htmlunit/WebClient.html#setCredentialsProvider(org.apache.commons.httpclient.auth.CredentialsProvider) http://htmlunit.sourceforge.net/apidocs/com/gargoylesoftware/htmlunit/DefaultCredentialsProvider.html ---------------------------------------------------------------------- Comment By: Robert Wittams (rjwittams) Date: 2003-07-18 17:38 Message: Logged In: YES user_id=270100 Surely the least ugly way to do this is to give WebClient a constructor taking an implementation of WebConnection. The setWebConnection is a pretty ugly way to do it imo... And deprecate the proxy settings constructor. Its misleading as it implies thats all the proxy settings you'll ever need. The cred stuff should just go. It either needs expanding to cover all the auth methods, which just duplicates HttpClient, or removal... I vote number 2. That kind of stuff is in my mind closely tied to the WebConnection, should be all part and parcel of that.. ---------------------------------------------------------------------- Comment By: Christian Sell (csell) Date: 2003-07-18 16:15 Message: Logged In: YES user_id=105319 a little comment: I have recently used HttpWebconnction to adapt HtmlUnit to another web client API (a descendant of W3Cs Jigsaw). I found this a rather easy process, despite the warnings about the "internal" character of HttpWebconnction. I would appreciate if this interface would remained intact - and maybe promoted to official status. HttpClient does have shortcomings, IMO. Christian ---------------------------------------------------------------------- Comment By: Mike Bowler (mbowler) Date: 2003-07-18 15:52 Message: Logged In: YES user_id=46756 The original plan was to completely isolate commons-httpclient so that it could be replaced if needed. At the time, it was not being actively maintained so this seemed a reasonable precaution. Today commons-httpclient is being very actively maintained so this decision doesn't make as much sense as it used to. Exposing the api isn't quite as simple as it sounds as there isn't a one-to-one mapping of WebClient to HttpClient. This was due to weaknesses in the httpclient api at the time the WebConnection was initially written. I believe that this could be changed today but it would require pretty much a rewrite of HttpWebConnection. I'll have to give this some thought. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=448269&aid=773552&group_id=47038 |
|
From: SourceForge.net <no...@so...> - 2005-05-10 14:39:39
|
Feature Requests item #773552, was opened at 2003-07-18 05:59 Message generated for change (Settings changed) made by yourgod You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=448269&aid=773552&group_id=47038 Category: None Group: None >Status: Closed Priority: 5 Submitted By: Robert Wittams (rjwittams) Assigned to: Nobody/Anonymous (nobody) Summary: Support proxy better - use http client more Initial Comment: Use http clients abilities more. The proxy server and credential apis are too simple. Eg NTLM auth, etc. Why not expose the HttpClient credential api? ---------------------------------------------------------------------- Comment By: Daniel Gredler (sdanig) Date: 2005-05-10 02:14 Message: Logged In: YES user_id=1109422 This feature request can probably be closed, as the feature has been implemented. http://htmlunit.sourceforge.net/apidocs/com/gargoylesoftware/htmlunit/WebClient.html#setCredentialsProvider(org.apache.commons.httpclient.auth.CredentialsProvider) http://htmlunit.sourceforge.net/apidocs/com/gargoylesoftware/htmlunit/DefaultCredentialsProvider.html ---------------------------------------------------------------------- Comment By: Robert Wittams (rjwittams) Date: 2003-07-18 16:38 Message: Logged In: YES user_id=270100 Surely the least ugly way to do this is to give WebClient a constructor taking an implementation of WebConnection. The setWebConnection is a pretty ugly way to do it imo... And deprecate the proxy settings constructor. Its misleading as it implies thats all the proxy settings you'll ever need. The cred stuff should just go. It either needs expanding to cover all the auth methods, which just duplicates HttpClient, or removal... I vote number 2. That kind of stuff is in my mind closely tied to the WebConnection, should be all part and parcel of that.. ---------------------------------------------------------------------- Comment By: Christian Sell (csell) Date: 2003-07-18 15:15 Message: Logged In: YES user_id=105319 a little comment: I have recently used HttpWebconnction to adapt HtmlUnit to another web client API (a descendant of W3Cs Jigsaw). I found this a rather easy process, despite the warnings about the "internal" character of HttpWebconnction. I would appreciate if this interface would remained intact - and maybe promoted to official status. HttpClient does have shortcomings, IMO. Christian ---------------------------------------------------------------------- Comment By: Mike Bowler (mbowler) Date: 2003-07-18 14:52 Message: Logged In: YES user_id=46756 The original plan was to completely isolate commons-httpclient so that it could be replaced if needed. At the time, it was not being actively maintained so this seemed a reasonable precaution. Today commons-httpclient is being very actively maintained so this decision doesn't make as much sense as it used to. Exposing the api isn't quite as simple as it sounds as there isn't a one-to-one mapping of WebClient to HttpClient. This was due to weaknesses in the httpclient api at the time the WebConnection was initially written. I believe that this could be changed today but it would require pretty much a rewrite of HttpWebConnection. I'll have to give this some thought. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=448269&aid=773552&group_id=47038 |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X