2. Edit httpd.conf to contain the following: LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_http_module modules/mod_proxy_http.so 3. Edit proxy.conf to contain the following: ProxyPass /ws/rta http://localhost:6099/rta ProxyPass /ws/rta/ http://localhost:6099/rta/ ProxyPassReverse /ws/rta http://localhost:6099/rta ProxyPassReverse /ws/rta/ http://localhost:6099/rta/ ProxyPass /ws/askt http://localhost:6099/askt ProxyPass /ws/askt/ http://localhost:6099/askt/ ProxyPassReverse /ws/askt http://localhost:6099/askt ProxyPassReverse /ws/askt/ http://localhost:6099/askt/ On Thu, Jul 10, 2008 at 2:38 PM, Benson Margulies <[EMAIL PROTECTED]> wrote: > I'm not the expert on jetty logging. However, I now realize, after trying > it, that I've been telling you the wrong thing about the browser > cross-scripting rules. > > I thought that it was true that, so long as one of the javascript files > came from a particular host:port combination, that you would be able to > connect back to it. > > I was wrong. The web service must be on the same host:port as the main HTML > page. > > So we're back to using rewrite rules. I have set up reverse proxies for > this purposes on Apache, but it was a very long time ago. I don't have any > clue how to do it on plain-old-jetty. > > You could also presumably use an invisible iframe to host a page that is > really on the same host as the web service, and get the data in and out of > there. > > I think I'll be able to post a rewrite recipe later today. > > > > On Thu, Jul 10, 2008 at 12:03 PM, Christine Karman <[EMAIL PROTECTED]> > wrote: > >> On Thu, 2008-07-10 at 07:38 -0400, Benson Margulies wrote: >> > Christine, >> > >> > I'm trying to find some time to build up an example. Until then, I >> > want to try to clarify something. >> > >> > The cxfjsutils.js file and the server itself have to be on the same >> > host:port. The rest of the html need not. >> >> The web service works ok and the javascript download from the web >> service works ok. But somewhere inside the javascript the call to the >> webservice doesn't work. Not on port 9000 and not on a rewritten /soap >> url. The error it gives suggests that the call is ok. >> Is there a way of activating the log in Jetty so I can see if Jetty >> receives the call? >> >> dagdag >> Christine >> >> >> On Wed, Jul 9, 2008 at 12:34 PM, Christine <[EMAIL PROTECTED]> >> wrote: >> Benson, >> this is what the js trace gives me: >> emptyClient constructorrequest >> http://www.christine.nl/soap/wendyBotabout to open POST >> http://www.christine.nl/soap/wendyBotabout to send dataPOST >> http://www.christine.nl/soap/wendyBotonreadystatechange >> 1onreadystatechange 2onreadystatechange 4onreadystatechange DONE >> 0 >> >> then it calls the error function with code -1. >> >> -- >> dagdag is just a two character rotation of byebye >> www.christine.nl >> >> >
