I hope you file this as a JIRA bug and include details for fixing it
etc... Great job tracking down the problem.

Wayne

On 4/26/06, Clifton Craig <[EMAIL PROTECTED]> wrote:
> On Wednesday 26 April 2006 11:42 am, Ben Short wrote:
> > Craig,
> >
> > I will post my setup to see if it helps you.
>
> I got it! I figured out the problem and I fixed it!! The problem was
> commons-httpclient. Maven-proxy ships with an older version than current.
> What I did was fire up groovyConsole and prototype the code that I found in
> maven-proxy's source base. I passed httpclient a URL to the offending pom
> from Ibiblio and I got a status code of 200 in my console. I then noted the
> different version of the httpclient api distributed with groovy vs. that
> which was found in the maven-proxy war file. I replaced my groovy httpclient
> jar with the exact one I found in the maven-proxy war and then I started
> getting the same "missing HTTP header" error I was getting in my Jetty logs.
> I then switched back to the later version (3.0-rc3) of HTTP client in both
> Groovy and maven-proxy and viola! The error went away! Thank you Ben and
> thank you Tom for all of your help!
>
> ---------------------------------------------------
> Clifton C. Craig, Software Engineer
> Intelligent Computer Systems - A Division of GBG
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to