Forums

I'm having a problem with Jade's HTMLDocuments in Apache. I have previously had a version working with IIS but I wanted to give it a go under Apache.

I have an initial logon form presented as the startup form - that part is fine. However when I do the post all that Jade is getting is the base html. I used Fiddler to capture the post request and I was able to see the other attributes being sent from the page (the following is shown in the textView Tab - "_ts=27+August+2012%2C+19%3A57%3A32&_jadeReferenceClass=IwfmLogin&_jadeReferenceDocument=IwfmLogin&_session=1fbf49bdb05fb6ea&formID=22262179553859&q4_logonId=usercode&q6_password=1234&website=&simple_spc=22262179553859-22262179553859").

I have reimplimented the processRequest and reply methods to just include a simple write for logging. The processRequest is not invoked. The Web Monitor window shows the request coming in - the query and http strings only have the application name.

Has anyone else had this problem (did you find the solution)? Is there something I could have missed in the jadehttp.conf?

Hi,
I run Apache on Linux and use JadeWebService Provider rather than JadeHTMLDocuments but I imagine the Apache setup is similar.

The relevant parts of the configuration in Apache (in a jade.conf file - probably your jadehttp.conf file) are

LoadModule jadehttp_module modules/mod_jadehttp.so

<IfModule mod_jadehttp.c>
<Location /jade-info>
SetHandler jadehttp-info
</Location>
<Location /URLAppName>
SetHandler jadehttp-handler
ApplicationType WebServices
Application JadeAppName
TcpConnection localhost 50500 3 3 ## 3 copies
JadeTimeout 1800 ## optional. There are some long transactions!!
PhysicalDirectory "/jadePictures" ## ironically, not a physical directory at all
</Location>
</IfModule>

<Directory "/jadePictures">
Order deny,allow
Allow from All
</Directory>

<Location /URLAppName>
Header set Cache-Control "no-cache"
Header set Pragma "no-cache"
</Location>
Alias /jadeImages "/jadePictures"


In the browser, a user connects to the app using the URL https://<DOMAIN>/URLAppName
The Jade app is called JadeAppName.

jadehttp routes all requests from the browser to the Jade app (port 50500 on localhost in my case), which runs as a server/ appserver app (3 copies). The very first request is simply "URLAppName", which is what you say you observed in the Monitor. I read the index.html file from disk and send that back as the response. In your case it would be the login form. Thereafter I get requests (JSON) as normal.

I'm not sure but it sounds like jadehttp isn't routing anything at all and Apache simply serving index.html like a normal page??

Hope that helps,
Brendan

Thanks for your reply Brendan. Turns out to be my mistake.

I had to reimplement the buildFormAction method. Standard method includes "jadehttp.dll"
e.g
http://server/virtualDir/jadehttp.dll?JadeAppName

With Apache this does not work, so I generated the string myself

problem was I was generating
http://server/virtualDir?JadeAppName

this should have been
http://server/virtualDir/?JadeAppName