Re: REST call failure on newer tomcat version/update

2014-12-23 Thread Sean Dawson
On Tue, Dec 23, 2014 at 7:57 PM, Christopher Schultz < ch...@christopherschultz.net> wrote: > So the web server (serving the HTML) is on one machine and the > application server (responding to the REST requests the GWT client > initiates) are on different machines? So the problem is with > Javascr

Re: REST call failure on newer tomcat version/update

2014-12-23 Thread Sean Dawson
On Tue, Dec 23, 2014 at 7:01 PM, André Warnier wrote: > > There are a number of open-source "proxy servlets" available from > third-parties, if you search Google for "java proxy servlet" e.g. > There is even a Tomcat WiKi article on the subject, mentioning some. > http://wiki.apache.org/tomcat/Se

Re: REST call failure on newer tomcat version/update

2014-12-23 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Sean, On 12/23/14 5:02 PM, Sean Dawson wrote: > Will go through and make more changes, but it looks like simply not > copying over the Transfer-Encoding header in the proxy enables > things to work with 53. > > Thank you very much to everyone for y

Re: REST call failure on newer tomcat version/update

2014-12-23 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Sean, On 12/23/14 5:08 PM, Sean Dawson wrote: > On Tue, Dec 23, 2014 at 4:59 PM, Christopher Schultz < > ch...@christopherschultz.net> wrote: > >> Are you worried about spamming the list or giving out too much >> information? > > Mostly the form

Re: REST call failure on newer tomcat version/update

2014-12-23 Thread André Warnier
Sean Dawson wrote: Will go through and make more changes, but it looks like simply not copying over the Transfer-Encoding header in the proxy enables things to work with 53. Thank you very much to everyone for your time and effort and assistance. Is there a clear/concise document on what to do

Re: REST call failure on newer tomcat version/update

2014-12-23 Thread Sean Dawson
On Tue, Dec 23, 2014 at 4:59 PM, Christopher Schultz < ch...@christopherschultz.net> wrote: > Are you worried about spamming the list or giving out too much > information? Mostly the former, but a tiny bit the latter. > somewhere in between the GWT client and theGWT server -- btw why are > you

Re: REST call failure on newer tomcat version/update

2014-12-23 Thread Sean Dawson
Will go through and make more changes, but it looks like simply not copying over the Transfer-Encoding header in the proxy enables things to work with 53. Thank you very much to everyone for your time and effort and assistance. Is there a clear/concise document on what to do / not do when it come

Re: REST call failure on newer tomcat version/update

2014-12-23 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Sean, On 12/23/14 4:38 PM, Sean Dawson wrote: > Thanks for the replies and the extra info. I've spent most of the > day but finally have a fairly self-contained, much simpler, example > that reproduces the issue between 52 and 53. > > Can I send th

Re: REST call failure on newer tomcat version/update

2014-12-23 Thread Sean Dawson
Thanks for the replies and the extra info. I've spent most of the day but finally have a fairly self-contained, much simpler, example that reproduces the issue between 52 and 53. Can I send this to someone directly rather than attach it here so everyone gets it? Regardless, I will make some chang

Re: Multiple instances?

2014-12-23 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Billy, On 12/19/14 1:37 PM, Billy Bones wrote: > For sure, do I need an account or something special? You can sign-up yourself. > Could you send me the wiki link? http://wiki.apache.org/tomcat/ Choose "login" at the top of the page and then choo

Re: REST call failure on newer tomcat version/update

2014-12-23 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Sean, On 12/22/14 8:19 PM, Sean Dawson wrote: > With 52, all calls seem to work and return quickly, fiddler doesn't > show any errors/warning. > > With 53, the one PUT call seems to return status code 0 on client > (hard to debug, in RestyGwt/javas

Re: [OT] REST call failure on newer tomcat version/update

2014-12-23 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Konstantin, On 12/23/14 2:18 PM, Konstantin Kolinko wrote: > 2014-12-23 22:06 GMT+03:00 Christopher Schultz >> >> Konstantin, >> >> On 12/23/14 11:12 AM, Konstantin Kolinko wrote: >>> >>> 2) I think that if getHeaders().get(header) returns a sing

Re: [OT] REST call failure on newer tomcat version/update

2014-12-23 Thread Konstantin Kolinko
2014-12-23 22:06 GMT+03:00 Christopher Schultz > > Konstantin, > > On 12/23/14 11:12 AM, Konstantin Kolinko wrote: >> >> 2) I think that if getHeaders().get(header) returns a single >> element, it would be better to use setHeader() method instead of >> addHeader() one. >> >> It is odd to call addHe

Re: [OT] REST call failure on newer tomcat version/update

2014-12-23 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Konstantin, On 12/23/14 11:12 AM, Konstantin Kolinko wrote: > 2014-12-23 18:18 GMT+03:00 Sean Dawson : >> On Tue, Dec 23, 2014 at 9:56 AM, André Warnier >> wrote: >> >>> As another wild guess, given what you mention above : maybe it is

Re: How to setup mod_jk to work with an Instance of CATALINA_BASE

2014-12-23 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Nikolaou, On 12/23/14 3:55 AM, Nikolas Nikolaou wrote: > Hi. I've managed to connect the default CATALINA_HOME tomcat > 8.0.15 with apache2 using mod_jk but I can't find Info on how to > connect to an Instance of CATALINA_BASE. What changes would

Re: REST call failure on newer tomcat version/update

2014-12-23 Thread Konstantin Kolinko
2014-12-23 18:18 GMT+03:00 Sean Dawson : > On Tue, Dec 23, 2014 at 9:56 AM, André Warnier wrote: > >> >>> As another wild guess, given what you mention above : maybe it is your >> "simple proxying webapp" which causes the problem ? >> As far as Tomcat is concerned, that /is/ the webapp which gener

Re: REST call failure on newer tomcat version/update

2014-12-23 Thread Sean Dawson
On Tue, Dec 23, 2014 at 9:56 AM, André Warnier wrote: > >> As another wild guess, given what you mention above : maybe it is your > "simple proxying webapp" which causes the problem ? > As far as Tomcat is concerned, that /is/ the webapp which generates the > response to the browser request. Tom

Re: REST call failure on newer tomcat version/update

2014-12-23 Thread André Warnier
Sean Dawson wrote: Thanks again for the reply. I forgot to mention last night that in the tomcat logs, that particular call has a 200 status code. (like fiddler said too) It seems RestyGwt and fiddler both have issues decoding the response (in 53) - but I don't know why, and everything I've see

Re: REST call failure on newer tomcat version/update

2014-12-23 Thread Sean Dawson
Thanks again for the reply. I forgot to mention last night that in the tomcat logs, that particular call has a 200 status code. (like fiddler said too) It seems RestyGwt and fiddler both have issues decoding the response (in 53) - but I don't know why, and everything I've seen so far indicates th

Re: How to setup mod_jk to work with an Instance of CATALINA_BASE

2014-12-23 Thread André Warnier
Nikolas Nikolaou wrote: Hi. I've managed to connect the default CATALINA_HOME tomcat 8.0.15 with apache2 using mod_jk but I can't find Info on how to connect to an Instance of CATALINA_BASE. What changes would I need to make to the workers file as to the location of tomcat_home. Hi. You m

Re: REST call failure on newer tomcat version/update

2014-12-23 Thread André Warnier
Sean Dawson wrote: Ok after many hours, here's all the information as I know it - as clearly and thoroughly as I can give it... One physical machine - Windows 7 Gwt 2.6.1 App deployed to tomcat 7 (either 52 or 53) built with maven 3.1.1 uses RestyGwt 1.4 uses ProxyServlet to pass REST cal

How to setup mod_jk to work with an Instance of CATALINA_BASE

2014-12-23 Thread Nikolas Nikolaou
Hi. I've managed to connect the default  CATALINA_HOME  tomcat 8.0.15 with apache2 using mod_jk but I can't find Info on how to connect to an Instance of CATALINA_BASE. What changes would I need to make to the workers file as to the location of tomcat_home.