topic Re: Name Virtualhost scenario in Alfresco Archive

Name Virtualhost scenario

matutano6 — Thu, 27 Feb 2014 20:41:48 GMT

Hi,I'm trying to configure a name based virtualhost with Apache Web Server doing reverse proxy to Tomcat where the Activiti Explorer is deployed.The "important" part of web server configuration is as followsroxyPass /activiti-explorer/ http://127.0.0.1:8080/activiti-explorer/ProxyPassReverse /acti

Re: Name Virtualhost scenario

matutano6 — Wed, 05 Mar 2014 14:49:55 GMT

Hi,
after a couple of days, I retry the login to investigate further and the login HTML was correct. I mean, the URL is still absolute, but the domain and port (and I assume that protocol will follow them if it were https) are the same as in the browser URL bar.

To be clear: none of the configurations were changed nor any component was restarted between the missbehavior of the last weekend and the correct one of today. I think then, it has something to do with some cachè mechanism. ¿Could you please tell me something about that to know as much as possible about the internals?

Thanks,
M.

Re: Name Virtualhost scenario

jbarrez — Mon, 10 Mar 2014 10:57:41 GMT

hmmm that sounds very odd. There is no caching whatsoever going on …

Can't it be an apache sync issue … ie it didn't know the server was online … or something in that area… just guessing.

Re: Name Virtualhost scenario

matutano6 — Mon, 10 Mar 2014 11:26:11 GMT

No, I don't think it was an apache issue because I made test directly to Tomcat using telnet/netcat and I was seeing that behavior.

It's solved now and working as expected. Nevertheless, I'd like to know how the absolute URL is build inside the Java application in case there's a J2EE container issue (with Tomcat?). Why not to use a relative URL?

Thanks,
M.

Re: Name Virtualhost scenario

jbarrez — Tue, 11 Mar 2014 12:29:41 GMT

The url is not absolute, it is dynamically built up, see the org.activiti.explorer.ui.login.ExplorerLoginForm class.

Re: Name Virtualhost scenario

matutano6 — Wed, 12 Mar 2014 14:03:29 GMT

I saw in Explorer's code that the URL is obtained by invoking com.vaadin.ui.LoginForm.getApplication().getURL(), so it's a Vaadin matter.

I have not look at Vaadin's code yet, but at least in the version of Vaadin distributed with Explorer 5.14, it returns an absoulte URL (begining from protocol). IMHO I would like to have a relative URL (without protocol and host, begining at the path part) in case of a scenario where the discovered absolute URL may be incorrect as in some cluster architectures.

With the information you gave me I know were to look at if I get in trouble with it, so thanks for your help!

Regards,
M.

Re: Name Virtualhost scenario

jbarrez — Mon, 17 Mar 2014 08:20:36 GMT

thanks for the information, an absolute URL there would indeed not be very good practice!