On 28/01/2010 16:17, Scott Wilson wrote:
On 28 Jan 2010, at 15:10, Henning Eriksson wrote:
Hi,
We solved the problem at the moment by making changes to the Wookie
proxy code. It now reads the Authorization from the Request header and
send it through the Proxy. Also finished the POST support. Busy at the
moment, and out of office next week, but after 8th of february we can
send in the fix as a patch.
That's fantastic, Henning, great work!
Note that you will need to send in an ICLA before we can apply the patch
- see http://apache.org/licenses/icla.txt
That depends on the IP contained in the patch. By the sounds of it there
is unlikely to be any significant IP contained in the patch. There for
submitting the patch via the issue tracker and being sure to check the
box saying it is intended for inclusion and permission is granted to use
it will be enough.
You can then submit the patch file as an attachment when you create an
issue in the tracker at:
http://issues.apache.org/jira/browse/WOOKIE
If you need any help with any of these steps, just ask on the list. (Or
I'll see you in Innsbruck next week perhaps?)
Ross
Best regards,
Henning Eriksson
Scott Wilson skrev 2010-01-27 14.07:
Hi Henning,
On 27 Jan 2010, at 09:56, Henning Eriksson wrote:
Hi,
We are working with Wookie in a project and need to send HTTP POST.
Will you add support for HTTP POST through the proxy? Today it only
send "XMLDATA-TODO" according to ProxyServlet.java.
The proxy uses commons HttpClient - it should be fairly
straightforward to finish the POST support; would you like to try
doing this yourself and send in the fix as a patch?
Another question is regarding doing Basic Auth through the Wookie
proxy. Will it be supported in the future? What would be the easiest
way to manage this?
At the moment it will translate a request containing a username and
password as parameters into a HTTP Basic Auth request, e.g.
proxy?url=http://myurl.com&username=usr&password=pwd
Though looking over the code I think there are plenty of areas for
improvement here.
(We had hoped we could reuse Shindig's proxy code, but sadly it was
wound too tightly into lots of other parts of Shindig and could not
be extracted into a standalone jar.)
S
Best regards,
Henning Eriksson
