On Fri, 2015-04-10 at 10:18 -0400, Karl Wright wrote: > Yes, I think we can manage. Thanks! > > Karl >
Done. http://svn.apache.org/r1672852 Oleg > > On Fri, Apr 10, 2015 at 9:50 AM, Oleg Kalnichevski <[email protected]> wrote: > > > On Thu, 2015-04-09 at 19:48 -0400, Karl Wright wrote: > > > Hi Oleg, > > > > > > I'm working to remove the numerous new 4.4 deprecation warnings in > > > ManifoldCF's web connector and ran into a serious problem. Heretofore, > > we > > > had been overriding an existing cookiespec class (BrowserCompatSpec) and > > > disabling the BasicPathHandler's validation in order to handle certain > > > web-sites that use cross-domain cookies. Unfortunately this is no longer > > > possible without putting the override class into > > > the org.apache.http.impl.cookie package. BrowserCompatSpec is > > deprecated, > > > and none of the non-deprecated cookiespec classes can be overridden in > > the > > > manner described. The reason that happens is because the basic > > constructor > > > supplied by abstract base class, which allows the handlers to be set, has > > > protected access. > > > > > > What is your recommendation for working around this problem? Is there a > > > way to do it without duplicating large chunks of code? > > > > > > > It is an oversight on my part. We could make RFC6265CookieSpecBase > > public or provide more compatibility levels in RFC6265CookieSpecProvider > > or both, but in 4.5. Can you, guys, live with older cookie specs until > > 4.5? > > > > Oleg > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
