Thank you very much for sharing this!

I am using the two first configurations lines for years and never had any problem but this is because in:
    ProxyPass /DIRE http://localhost:8080/DIRE
    ProxyPassReverse /DIRE http://localhost:8080/DIRE
the path is not changing, just the host.

Tricky the life of the computer scientist!

Good luck with your wiki!

Christophe

Le 12/05/2012 04:59, Mariano Rico a écrit :
Hi! at last good news!!!

I solved!! It was the cookie path
In my tomcat, jspwiki was in the context /DBpediaES, and the session
persitence mechanism creates a JSESSIONID with path /DBpediaES
However, from the internet this application runs on /  (my proxy converts
http://es.dbpedia.org/ to http://mymachine:8080/DBpediaES). Therefore the
cookie path that should see a given browser is /

Therefore, the missing linen is the third one:
ProxyPass        / http://150.244.59.12:8080/DBpediaES/
ProxyPassReverse / http://150.244.59.12:8080/DBpediaES/
*ProxyPassReverseCookiePath /DBpediaES /*
*
*
Finally!!! I realized using Firebug (to see the cookies) from outside of my
machine (from home).

I hope this help to many of us.

Best regards,

-- Mariano
------------------------------------------------------
   Mariano Rico<http://www.ii.uam.es/~mrico>
   Computer Science Dept<http://www.ii.uam.es/>.
   Universidad Autónoma de Madrid<http://www.uam.es/>
   Spain



On Mon, May 7, 2012 at 11:42 PM, Juan Pablo Santos Rodríguez<
juanpablo.san...@gmail.com>  wrote:

Hi Mariano,

the style absolute option should enable an easy mod_rewrite. As for the
rest of resources, take a look at
https://issues.apache.org/jira/browse/JSPWIKI-181 , hopefully it can help
with the missing static resources.

Regarding the proxy issue, if you can log not going through Apache but you
can't when going through it, I would go down for Apache logs to see what's
happening (maybe you have a proxy which denies outbound connections or
something weird like that?).


br,
juan pablo


On Mon, May 7, 2012 at 12:11 PM, Mariano Rico<mariano.r...@uam.es>  wrote:

Hi Juan Pablo,

I am very sorry for being missing so long. Thanks a lot for your support.
However, the problems remain even after applying your recipe :-)

the Style absolute option in jspwiki.properties recovers some icons, but
the site layout is still "linearized".

Concerning the proxy, the problem with the disappeared trail and
the impossibility of logging-in still remain :-(
I will check the cookies. Stay tuned :-)

Best regards,

-- Mariano
------------------------------------------------------
  Mariano Rico<http://www.ii.uam.es/~mrico>
  Computer Science Dept<http://www.ii.uam.es/>.
  Universidad Autónoma de Madrid<http://www.uam.es/>
  Spain



On Sun, Mar 11, 2012 at 11:16 PM, Juan Pablo Santos Rodríguez<
juanpablo.san...@gmail.com>  wrote:

Hi again Mariano,

one more thing to test I've just noticed: search for
jspwiki.referenceStyle
in your jspwiki.properties file, and set it to "absolute", without
quotes.
This should append jspwiki.baseUrl to the links generated by JSPWiki
(static resources links amongst others), which should ease you a lot
its
resolution., i.e.: option#1 below should be enough to have your JSPWiki
instance correctly seen through tomcat and through apache.


HTH,
juan pablo


2012/3/10 Juan Pablo Santos Rodríguez<juanpablo.san...@gmail.com>

Hello Mariano,

there are two possible ways of setting your JSPWiki instance up:
1.- baseUrl pointing to es.dbpedia.org: in this case you won't be
able
to
see a nice JSPWiki when going directly through tomcat; resources are
requested to /templates/whatever instead of
/DBPediaES/templates/whatever.
That's why you don't get the decorated pages when going directly
through
tomcat.

2.- baseUrl pointing to http://asera.ii.uam.es:8080/DBpediaES: With
your
current Apache2 configuration, it's the opposite situation. In this
case
resources (through Apache2) will be requested to
http://es.dbpedia.org/DBPediaES/templates/whatever

I think that your best option goes with sticking to option #2, as it
is
the only one which will enable you to have your JSPWiki nicely seen
in
both
cases.

Once you have your JSPWiki instance configured to be seen through
plain
tomcat, the next step should be tweak your Apache configuration. You
should
need your ProxyRequest(Reverse) directives as they are now, plus some
more
extra configuration. I don't know in detail the internals of the
apache2
configuration, but may be an Alias directive to map /DBPediaES
requests
to
/ [1] or some mod_rewrite configuration ([2], [3]) will be enough to
do
the
trick.


regards,
juan pablo

[1]: http://httpd.apache.org/docs/2.2/mod/mod_alias.html
[2]: http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html
[3]: http://httpd.apache.org/docs/2.2/rewrite/remapping.html



On Sat, Mar 10, 2012 at 11:57 AM, Mariano Rico<mariano.r...@uam.es
wrote:

Dear Juan,

thanks a lot for your help.
See my comments inline


in fact, that Apache serves http://192.168.3.13:80 In any case,
you
(=we,
here at the office) obtain the same results going either through
http://192.168.3.13:80/JSPWiki or
http://192.168.3.13:8085/JSPWikior
http://ic.softwarefactory.entelgy.com/JSPWiki


I can not see those sites though Internet :-S
Are they down?


just to be sure, some more questions:
- when you access your JSPWiki instance, bypassing your apache,
you're
going through http://asera.ii.uam.es:8080/DBpediaES isn't it?

right


To where is
pointing your jspwiki.baseUrl? It should point to
http://asera.ii.uam.es:8080/DBpediaES/

No. It is pointing es.dbpedia.org


This way you would get nice
decorated pages on your JSPWiki instance when going only through
tomcat.

If baseURl is http://asera.ii.uam.es:8080/DBpediaES/ the access
through
http://asera.ii.uam.es:8080/DBpediaES/ will work, but the access
through
es.dbpedia will fail (will show the non decorated pages)



Once you've get into there, your current ProxyPass(Reverse)
directives
should map / to your running JSPWiki instance:
ProxyPass / http://150.244.59.12:8080/DBpediaES/
ProxyPassReverse / http://150.244.59.12:8080/DBpediaES/


Yes, it is so now


The only thing I'm not very sure is if you are going to need some
mod_rewrite in order to make all links go through your Apache..


No clue :-(

Thanks a lot for your time and support.

Best regards,

-Mariano



Reply via email to