hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Wright <daddy...@gmail.com>
Subject Re: Cannot extend CookieSpec classes due to protected constructor
Date Fri, 10 Apr 2015 14:18:53 GMT
Yes, I think we can manage.  Thanks!

Karl


On Fri, Apr 10, 2015 at 9:50 AM, Oleg Kalnichevski <olegk@apache.org> 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: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message