Leon, Ed
Thanks for looking at this. I realized I have an apache2 problem at this
stage more than a GWT one.
A bit of proxy code in tomcat and apache2 + enabling proxy_http has fixed
the problem. Most of my enlightenment came from
i think gwt has a same source domain filter
On Thu, Nov 9, 2023 at 11:47 AM Leon wrote:
> As far as I know, gwt uses relative paths wrt it's own context root. So
> the client calls should always be able to reach the gwt servlets. I've
> never had to configure anything to make that happen.
> If
As far as I know, gwt uses relative paths wrt it's own context root. So
the client calls should always be able to reach the gwt servlets. I've
never had to configure anything to make that happen.
If you setup apache2 to forward virtual name based hosts to tomcat, apache2
is nothing more than a
yeah that sounds doable, I think it's along the lines I was already thinking
So* mydomain..com* is served by apache2 and includes the GWT javascript
Apache2 also has a conf for *subdomain.mydomain.com* that creates a
backend AJP to tomcat where I serve subdomain.*mydomain.com/appA* and
You can deploy the web application on tomcat and use mod_proxy on apache2
to forward https (or http if required) to tomcat on 8080 (or another port
if required)
Op woensdag 8 november 2023 om 18:31:19 UTC+1 schreef dav...@googlemail.com:
> hi Ed
>
> Yes understood and most of the "app" is GWT
hi Ed
Yes understood and most of the "app" is GWT produced javascript, part of a
web page, which I've always run on apache2 and don't really want to change
that for the ip address supplying servelet which is a recent addition. I
already also run a backend tomcat with an AJP connection to
jetty is application server while apache2 is a web server. tomcat is the
apache app server.
On Wed, Nov 8, 2023 at 4:48 AM 'dav...@googlemail.com' via GWT Users <
google-web-toolkit@googlegroups.com> wrote:
> On my development machine I test my code in jetty. The client code calls a
> server
On my development machine I test my code in jetty. The client code calls a
server to get the client ip address. This works fine and I see a server at
localhost:8080/foo/bar as I expect. If I browse to it I get a 405 as GET
request are not allowed, but that's not a problem as it does the job
