You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jspwiki.apache.org by Mariano Rico <ma...@gmail.com> on 2012/03/05 17:08:34 UTC
After Apache front-end: no log in, no trail
Hi all,
I installed JSPWiki 2.8.4 in my machine (asera.ii.uam.es:8080/DBpediaES),
and everything was perfect.
However, when I did set up Apache (v 2.2) as front-end (with ProxyPass and
proxyPassReverse) pointing to this wiki, the log in mechanism disappeared.
I can not log in, but I get no errors in the log, and the "Your trail:" is
not working (it is emptly).
I had to change the BaseURL to es.dbpedia.org, what results in a "no css"
version running at asera.ii.uam.es:8080/DBpediaES but a good presentation
for es.dbpedia.org ¿Is this the usual way? I thought that the Apache
front-end should not modify the behavior of JSPWiki, ans I could use both
"instances".
¿Any suggestion?
Best regards,
-Mariano
Re: After Apache front-end: no log in, no trail
Posted by Mariano Rico <ma...@uam.es>.
Hi Florian,
if you try it, please, let me know it.
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 Tue, Mar 6, 2012 at 20:09, Florian Holeczek <fl...@holeczek.de> wrote:
> Hi Mariano,
>
> > Another issue is the "entry point". I see in your config that the entry
> > point is /JSPWiki. In my case is /
> > Do you know if this can be a problem?
>
> Good point! According to your first mail, you want to map / to DBpediaES/
> Could be that this is a problem, haven't tried this case yet!
>
> Regards
> Florian
>
Re: After Apache front-end: no log in, no trail
Posted by Christophe Dupriez <du...@squadratic.com>.
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.santos@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<ma...@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.santos@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<ju...@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.rico@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
>>>>>>
>>>>>
Re: After Apache front-end: no log in, no trail
Posted by Juan Pablo Santos Rodríguez <ju...@gmail.com>.
Hola Mariano,
hey nice to hear that :) Would you mind updating [1] and/or [2] with that
information? these are the first places in which people do look when
they're configuring their JSPWiki behind an Apache server.
thanks & regards,
juan pablo
[1]: http://www.jspwiki.org/wiki/ApacheTomcatConnection
[2]: http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
On Sat, May 12, 2012 at 4:59 AM, Mariano Rico <ma...@uam.es> wrote:
> 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.santos@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 <ma...@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.santos@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 <ju...@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.rico@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
> > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
>
Re: After Apache front-end: no log in, no trail
Posted by Mariano Rico <ma...@uam.es>.
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.santos@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 <ma...@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.santos@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 <ju...@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.rico@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
> > > >>
> > > >
> > > >
> > >
> >
>
Re: After Apache front-end: no log in, no trail
Posted by Juan Pablo Santos Rodríguez <ju...@gmail.com>.
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 <ma...@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.santos@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 <ju...@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.rico@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
> > >>
> > >
> > >
> >
>
Re: After Apache front-end: no log in, no trail
Posted by Mariano Rico <ma...@uam.es>.
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.santos@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 <ju...@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.rico@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/JSPWiki or
> >> > 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
> >>
> >
> >
>
Re: After Apache front-end: no log in, no trail
Posted by Juan Pablo Santos Rodríguez <ju...@gmail.com>.
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 <ju...@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 <ma...@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/JSPWiki or
>> > 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
>>
>
>
Re: After Apache front-end: no log in, no trail
Posted by Juan Pablo Santos Rodríguez <ju...@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 <ma...@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/JSPWiki or
> > 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
>
Re: After Apache front-end: no log in, no trail
Posted by Mariano Rico <ma...@uam.es>.
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/JSPWiki or
> 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
Re: After Apache front-end: no log in, no trail
Posted by Juan Pablo Santos Rodríguez <ju...@gmail.com>.
Hi,
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/JSPWiki or
http://ic.softwarefactory.entelgy.com/JSPWiki
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? To where is
pointing your jspwiki.baseUrl? It should point to
http://asera.ii.uam.es:8080/DBpediaES/ This way you would get nice
decorated pages on your JSPWiki instance when going only through tomcat.
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/
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..
regards,
juan pablo
On Fri, Mar 9, 2012 at 12:27 PM, Mariano Rico <ma...@uam.es> wrote:
> Hi Pablo,
>
>
> I will try this and will let you know. Thanks a million.
> >
>
> Confirmed. It does not solve my problem :-(
>
> Best regards,
>
> -Mariano
>
Re: After Apache front-end: no log in, no trail
Posted by Mariano Rico <ma...@uam.es>.
Hi Pablo,
I will try this and will let you know. Thanks a million.
>
Confirmed. It does not solve my problem :-(
Best regards,
-Mariano
Re: After Apache front-end: no log in, no trail
Posted by Mariano Rico <ma...@uam.es>.
Hi Pablo,
joining inlines from previous e-mail:
>
> You should (now) be able to login, create a user, etc. at
> http://ic.softwarefactory.entelgy.com/JSPWiki/
>
>
¡¡Incredible!! I can register and login in you site :-)
> The config used (in this case) was the previously mentioned:
> - jspwiki.baseURL points to http://ic.softwarefactory.entelgy.com/JSPWiki/
> - relevant Apache2 configuration:
> <Location /JSPWiki>
> Order Deny,Allow
> Deny from all
> Allow from All
> ProxyPass http://192.168.3.12:8085/JSPWiki
> SetEnv force-proxy-request-1.0 1
> SetEnv proxy-nokeepalive 1
> ProxyPassReverse http://192.168.3.12:8085/JSPWiki
> </Location>
>
>
It is remarcable:
1) In the proxy (pass and passReverse) you use the IP instead of the URL
2) You use a /something instead of my simple /
I will try this and will let you know. Thanks a million.
> Your Apache2 configuration looks good to me. However, looking at the source
> code of http://asera.ii.uam.es:8080/DBpediaES , the static resources are
> being requested at, i.e.,
> http://asera.ii.uam.es:8080/templates/default/jspwiki.css instead of being
> requested to http://es.dbpedia.org/templates/default/jspwiki.css , it
> seems
> that jspwiki.baseUrl hasn't been picked up. Can you redeploy the
> application and delete the tomcat's work folder in order to enforce the new
> JSPWiki configuration?
>
>
If I go to your http://192.168.3.12:8085/JSPWiki I get an error message. I
guess that that direction is internal. Could you check if you see an
ordiray JSPWiki if you browse to http://192.168.3.12:8085/JSPWiki ?
> Also, do you have mod_rewrite enabled?
>
>
I will check... apache should warn, is'n it?
Thanks a lot for you patience and support.
Best regards,
-Mariano
Re: After Apache front-end: no log in, no trail
Posted by Juan Pablo Santos Rodríguez <ju...@gmail.com>.
Hello Mariano,
On Wed, Mar 7, 2012 at 6:43 PM, Mariano Rico <ma...@uam.es> wrote:
> Hi Juan,
>
> I think some inlines have been mixed :-(
>
joining inlines from previous e-mail:
You should (now) be able to login, create a user, etc. at
http://ic.softwarefactory.entelgy.com/JSPWiki/
The config used (in this case) was the previously mentioned:
- jspwiki.baseURL points to http://ic.softwarefactory.entelgy.com/JSPWiki/
- relevant Apache2 configuration:
<Location /JSPWiki>
Order Deny,Allow
Deny from all
Allow from All
ProxyPass http://192.168.3.12:8085/JSPWiki
SetEnv force-proxy-request-1.0 1
SetEnv proxy-nokeepalive 1
ProxyPassReverse http://192.168.3.12:8085/JSPWiki
</Location>
Your Apache2 configuration looks good to me. However, looking at the source
code of http://asera.ii.uam.es:8080/DBpediaES , the static resources are
being requested at, i.e.,
http://asera.ii.uam.es:8080/templates/default/jspwiki.css instead of being
requested to http://es.dbpedia.org/templates/default/jspwiki.css , it seems
that jspwiki.baseUrl hasn't been picked up. Can you redeploy the
application and delete the tomcat's work folder in order to enforce the new
JSPWiki configuration?
Also, do you have mod_rewrite enabled?
HTH,
juan pablo
>
> > OK. Let me know it.
> > >
> >
> > Try now, you should be able to login
> >
> >
> What ULR?
>
>
> > > internal links.
> > > Now, baseURL=es.dbpedia.org
> > > As fas a I know, that is why http://asera.ii.uam.es:8080/DBpediaES is
> > not
> > > working
> > >
> > >
> > The Apache2 configuration looks good to me. However, looking at the
> source
> > code of http://asera.ii.uam.es:8080/DBpediaES , the static resources are
> > being requested at, i.e.,
> > http://asera.ii.uam.es:8080/templates/default/jspwiki.css instead of
> being
> > requested to http://es.dbpedia.org/templates/default/jspwiki.css so it
> > seems that jspwiki.baseUrl hasn't been picked up. Can you redeploy the
> > application and delete the tomcat's work folder in order to enforce the
> new
> > JSPWiki configuration?
>
>
> The BaseURL specified in jspwiki,properties is set to
> http://es.dbpedia.org
> I thought that was the reason.
>
> Best regards,
>
> -Mariano
>
Re: After Apache front-end: no log in, no trail
Posted by Mariano Rico <ma...@uam.es>.
Hi Juan,
I think some inlines have been mixed :-(
> OK. Let me know it.
> >
>
> Try now, you should be able to login
>
>
What ULR?
> > internal links.
> > Now, baseURL=es.dbpedia.org
> > As fas a I know, that is why http://asera.ii.uam.es:8080/DBpediaES is
> not
> > working
> >
> >
> The Apache2 configuration looks good to me. However, looking at the source
> code of http://asera.ii.uam.es:8080/DBpediaES , the static resources are
> being requested at, i.e.,
> http://asera.ii.uam.es:8080/templates/default/jspwiki.css instead of being
> requested to http://es.dbpedia.org/templates/default/jspwiki.css so it
> seems that jspwiki.baseUrl hasn't been picked up. Can you redeploy the
> application and delete the tomcat's work folder in order to enforce the new
> JSPWiki configuration?
The BaseURL specified in jspwiki,properties is set to http://es.dbpedia.org
I thought that was the reason.
Best regards,
-Mariano
Re: After Apache front-end: no log in, no trail
Posted by Juan Pablo Santos Rodríguez <ju...@gmail.com>.
Hi Mariano,
some more comments inline:
On Wed, Mar 7, 2012 at 1:31 PM, Mariano Rico <ma...@uam.es> wrote:
> Hi Juan Pablo,
>
>
> don't know if the SetEnv commands are mandatory or not, all the
> > apache2-related actions were performed by our systems administrator, so
> I'm
> > not really sure; as for the domain issue, entel.es was our old domain,
> it
> > seems that the change to the new one hasn't been pushed into prod..
> should
> > talk with our admin one of these days..
>
>
>
> OK. Let me know it.
>
Try now, you should be able to login
>
>
> > anyway, if you manually change
> > entel.es to entelgy.com after sending the registration form, you should
> be
> > able to use your new account.
> >
> > Our entry point is /JSPWiki only because we have some other services
> > published under that domain, but now that you say it, I recall seeing
> this
> > morning that http://asera.ii.uam.es:8080/DBpediaES was translated into
> > http://es.dbpedia.org:8080/ and debugging with firebug I could see that
> > the
> > missing static resources where requested at, i.e,
> > http://es.dbpedia.org:8080/templates/* instead of
> > http://es.dbpedia.org:8080/DBpediaES/templates/* (or
> > http://es.dbpedia.org/templates/*) so may be there is some Apache2
> > configuration fiddling in :-?
>
>
>
> This is due to the jspwiki.baseURL
> It is mandatory to assign the real URL in order to provide the apropriate
> internal links.
> Now, baseURL=es.dbpedia.org
> As fas a I know, that is why http://asera.ii.uam.es:8080/DBpediaES is not
> working
>
>
The Apache2 configuration looks good to me. However, looking at the source
code of http://asera.ii.uam.es:8080/DBpediaES , the static resources are
being requested at, i.e.,
http://asera.ii.uam.es:8080/templates/default/jspwiki.css instead of being
requested to http://es.dbpedia.org/templates/default/jspwiki.css so it
seems that jspwiki.baseUrl hasn't been picked up. Can you redeploy the
application and delete the tomcat's work folder in order to enforce the new
JSPWiki configuration?
>
> > Can you send an extract of the configuration
> > of your apache2 conf file?
> >
> >
> I do not use conf file. Instead I use the default site (*
> /etc/apache2/sites-available/default)*. This is the content:
>
> *<VirtualHost *:80>
> ServerAdmin mariano.rico@gmail.com
>
> ProxyRequests Off
> ProxyPreserveHost On
>
> ProxyPass /sparql http://150.244.59.12:8890/sparql
> ProxyPassReverse /sparql http://150.244.59.12:8890/sparql
>
> #ProxyPass / ajp://150.244.59.12:8009/DBpediaES/
> #ProxyPassReverse / ajp://150.244.59.12:8009/DBpediaES/
> <about:blank>
>
> ProxyPass / http://150.244.59.12:8080/DBpediaES/
> ProxyPassReverse / http://150.244.59.12:8080/DBpediaES/
>
> <Proxy *>
> Order deny,allow
> allow from all
> </Proxy>
>
> DocumentRoot /var/www
> <Directory />
> Options FollowSymLinks
> AllowOverride None
> #allow from all
> </Directory>
> <Directory /var/www/>
> Options Indexes FollowSymLinks MultiViews
> AllowOverride None
> Order allow,deny
> allow from all
> </Directory>
> ...
> ...
> </VirtualHost>*
>
regards,
juan pablo
Re: After Apache front-end: no log in, no trail
Posted by Mariano Rico <ma...@uam.es>.
Hi Juan Pablo,
don't know if the SetEnv commands are mandatory or not, all the
> apache2-related actions were performed by our systems administrator, so I'm
> not really sure; as for the domain issue, entel.es was our old domain, it
> seems that the change to the new one hasn't been pushed into prod.. should
> talk with our admin one of these days..
OK. Let me know it.
> anyway, if you manually change
> entel.es to entelgy.com after sending the registration form, you should be
> able to use your new account.
>
> Our entry point is /JSPWiki only because we have some other services
> published under that domain, but now that you say it, I recall seeing this
> morning that http://asera.ii.uam.es:8080/DBpediaES was translated into
> http://es.dbpedia.org:8080/ and debugging with firebug I could see that
> the
> missing static resources where requested at, i.e,
> http://es.dbpedia.org:8080/templates/* instead of
> http://es.dbpedia.org:8080/DBpediaES/templates/* (or
> http://es.dbpedia.org/templates/*) so may be there is some Apache2
> configuration fiddling in :-?
This is due to the jspwiki.baseURL
It is mandatory to assign the real URL in order to provide the apropriate
internal links.
Now, baseURL=es.dbpedia.org
As fas a I know, that is why http://asera.ii.uam.es:8080/DBpediaES is not
working
> Can you send an extract of the configuration
> of your apache2 conf file?
>
>
I do not use conf file. Instead I use the default site (*
/etc/apache2/sites-available/default)*. This is the content:
*<VirtualHost *:80>
ServerAdmin mariano.rico@gmail.com
ProxyRequests Off
ProxyPreserveHost On
ProxyPass /sparql http://150.244.59.12:8890/sparql
ProxyPassReverse /sparql http://150.244.59.12:8890/sparql
#ProxyPass / ajp://150.244.59.12:8009/DBpediaES/
#ProxyPassReverse / ajp://150.244.59.12:8009/DBpediaES/<about:blank>
ProxyPass / http://150.244.59.12:8080/DBpediaES/
ProxyPassReverse / http://150.244.59.12:8080/DBpediaES/
<Proxy *>
Order deny,allow
allow from all
</Proxy>
DocumentRoot /var/www
<Directory />
Options FollowSymLinks
AllowOverride None
#allow from all
</Directory>
<Directory /var/www/>
Options Indexes FollowSymLinks MultiViews
AllowOverride None
Order allow,deny
allow from all
</Directory>
...
...
</VirtualHost>*
Re: After Apache front-end: no log in, no trail
Posted by Juan Pablo Santos Rodríguez <ju...@gmail.com>.
Hello Mariano,
don't know if the SetEnv commands are mandatory or not, all the
apache2-related actions were performed by our systems administrator, so I'm
not really sure; as for the domain issue, entel.es was our old domain, it
seems that the change to the new one hasn't been pushed into prod.. should
talk with our admin one of these days.. anyway, if you manually change
entel.es to entelgy.com after sending the registration form, you should be
able to use your new account.
Our entry point is /JSPWiki only because we have some other services
published under that domain, but now that you say it, I recall seeing this
morning that http://asera.ii.uam.es:8080/DBpediaES was translated into
http://es.dbpedia.org:8080/ and debugging with firebug I could see that the
missing static resources where requested at, i.e,
http://es.dbpedia.org:8080/templates/* instead of
http://es.dbpedia.org:8080/DBpediaES/templates/* (or
http://es.dbpedia.org/templates/*) so may be there is some Apache2
configuration fiddling in :-? Can you send an extract of the configuration
of your apache2 conf file?
regards,
juan pablo
On Tue, Mar 6, 2012 at 6:29 PM, Mariano Rico <ma...@uam.es> wrote:
> Hi Juan Pablo,
>
>
> we've also set up a JSPWiki instance behind an Apache server at work, and
> > we haven't had any problems:
> >
> > - jspwiki.baseURL points to
> http://ic.softwarefactory.entelgy.com/JSPWiki/
> > - relevant Apache2 configuration:
> > <Location /JSPWiki>
> > Order Deny,Allow
> > Deny from all
> > Allow from All
> > ProxyPass http://192.168.3.12:8085/JSPWiki
> > SetEnv force-proxy-request-1.0 1
> > SetEnv proxy-nokeepalive 1
> > ProxyPassReverse http://192.168.3.12:8085/JSPWiki
> > </Location>
> >
> >
>
> I have noticed in your code the SetEnv commands. I have copied to my
> configuration... with no results :-(
> Are sure these commands are required in your configuration?
>
> Another issue is the "entry point". I see in your config that the entry
> point is /JSPWiki. In my case is /
> Do you know if this can be a problem?
>
>
> > you can also check http://www.jspwiki.org/wiki/ApacheTomcatConnection to
> > see if it helps you
> >
> >
> Thanks a lot. I can not see anything relevant,. I tried
> the emptySessionPath="true" in the Connector, as well as the proxyName="
> www.your-domain.com". Neither could solve the problem :-(
>
> -- 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
>
Re: After Apache front-end: no log in, no trail
Posted by Florian Holeczek <fl...@holeczek.de>.
Hi Mariano,
> Another issue is the "entry point". I see in your config that the entry
> point is /JSPWiki. In my case is /
> Do you know if this can be a problem?
Good point! According to your first mail, you want to map / to DBpediaES/
Could be that this is a problem, haven't tried this case yet!
Regards
Florian
Re: After Apache front-end: no log in, no trail
Posted by Mariano Rico <ma...@uam.es>.
Hi Juan Pablo,
we've also set up a JSPWiki instance behind an Apache server at work, and
> we haven't had any problems:
>
> - jspwiki.baseURL points to http://ic.softwarefactory.entelgy.com/JSPWiki/
> - relevant Apache2 configuration:
> <Location /JSPWiki>
> Order Deny,Allow
> Deny from all
> Allow from All
> ProxyPass http://192.168.3.12:8085/JSPWiki
> SetEnv force-proxy-request-1.0 1
> SetEnv proxy-nokeepalive 1
> ProxyPassReverse http://192.168.3.12:8085/JSPWiki
> </Location>
>
>
I have noticed in your code the SetEnv commands. I have copied to my
configuration... with no results :-(
Are sure these commands are required in your configuration?
Another issue is the "entry point". I see in your config that the entry
point is /JSPWiki. In my case is /
Do you know if this can be a problem?
> you can also check http://www.jspwiki.org/wiki/ApacheTomcatConnection to
> see if it helps you
>
>
Thanks a lot. I can not see anything relevant,. I tried
the emptySessionPath="true" in the Connector, as well as the proxyName="
www.your-domain.com". Neither could solve the problem :-(
-- 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
RE: After Apache front-end: no log in, no trail
Posted by "Lannaud, Eric" <E....@unesco.org>.
My configuration:
On my Linux ubuntu 10.04 Lucid, the package:
libapache2-mod-jk 1:1.2.28-2 Apache 2 connector for the Tomcat Java servlet
see the documentation: http://tomcat.apache.org/connectors-doc
*******************************************************************************************
-------------------
| Frontal WEB |
-------------------
|Module JK| <---- file /etc/libapache2-mod-jk/workers.properties
|
| port 8009
|
------------------------
| Tomcat APPs Server | x N servers
------------------------
*******************************************************************************************
Ce fichier /etc/libapache2-mod-jk/workers.properties describe the conf application server. "ajp13_worker" connector plugs the localhost port 8009.
*******************************************************************************************
workers.tomcat_home=/usr/share/tomcat5
workers.java_home=/usr/lib/jvm/java-gcj
ps=/
worker.list=ajp13_worker
worker.ajp13_worker.port=8009
worker.ajp13_worker.host=localhost
worker.ajp13_worker.type=ajp13
worker.ajp13_worker.lbfactor=1
worker.loadbalancer.type=lb
worker.loadbalancer.balance_workers=ajp13_worker
*******************************************************************************************
Dans la conf Apache, sur Ubuntu nous l'avons mit dans /etc/apache2/httpd.conf
*******************************************************************************************
JkWorkersFile /etc/libapache2-mod-jk/workers.properties
JkLogFile /var/log/apache2/mod_jk.log
JkShmFile /var/log/apache2/mod_jk.shm
JkLogLevel info
*******************************************************************************************
Into an VH apache conf:
JkMount /wiki/* ajp13_worker
<Location /wiki>
<Limit GET POST>
order deny,allow
deny from all
Allow from 10
Allow from 172.24
Allow from 172.16
Allow from 172.25
Satisfy any
</Limit>
</Location>
*******************************************************************************************
E.
-----Original Message-----
From: Juan Pablo Santos Rodríguez [mailto:juanpablo.santos@gmail.com]
Sent: mardi 6 mars 2012 14:31
To: jspwiki-dev@incubator.apache.org; mariano.rico@uam.es
Subject: Re: After Apache front-end: no log in, no trail
Hello Mariano,
we've also set up a JSPWiki instance behind an Apache server at work, and we haven't had any problems:
- jspwiki.baseURL points to http://ic.softwarefactory.entelgy.com/JSPWiki/
- relevant Apache2 configuration:
<Location /JSPWiki>
Order Deny,Allow
Deny from all
Allow from All
ProxyPass http://192.168.3.12:8085/JSPWiki SetEnv force-proxy-request-1.0 1 SetEnv proxy-nokeepalive 1 ProxyPassReverse http://192.168.3.12:8085/JSPWiki </Location>
you can also check http://www.jspwiki.org/wiki/ApacheTomcatConnection to see if it helps you
regards,
juan pablo
On Tue, Mar 6, 2012 at 12:36 PM, Mariano Rico <ma...@uam.es> wrote:
> Hi Florian,
>
>
>
> > deciding for one "entry point" and configuring this the baseURL is
> > the
> way
> > to go.
> >
>
> Have you had this running? With login? Please, tell me how... :-)
>
>
> > BTW, any reason against using mod_proxy_ajp?
> >
> >
> I tried that at first, but it produced an error. It seems to be a
> versions incompatibility (Tomcat-Apache) identified problem :-(
>
> -- 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
>
Re: After Apache front-end: no log in, no trail
Posted by Juan Pablo Santos Rodríguez <ju...@gmail.com>.
Hello Mariano,
we've also set up a JSPWiki instance behind an Apache server at work, and
we haven't had any problems:
- jspwiki.baseURL points to http://ic.softwarefactory.entelgy.com/JSPWiki/
- relevant Apache2 configuration:
<Location /JSPWiki>
Order Deny,Allow
Deny from all
Allow from All
ProxyPass http://192.168.3.12:8085/JSPWiki
SetEnv force-proxy-request-1.0 1
SetEnv proxy-nokeepalive 1
ProxyPassReverse http://192.168.3.12:8085/JSPWiki
</Location>
you can also check http://www.jspwiki.org/wiki/ApacheTomcatConnection to
see if it helps you
regards,
juan pablo
On Tue, Mar 6, 2012 at 12:36 PM, Mariano Rico <ma...@uam.es> wrote:
> Hi Florian,
>
>
>
> > deciding for one "entry point" and configuring this the baseURL is the
> way
> > to go.
> >
>
> Have you had this running? With login? Please, tell me how... :-)
>
>
> > BTW, any reason against using mod_proxy_ajp?
> >
> >
> I tried that at first, but it produced an error. It seems to be a versions
> incompatibility (Tomcat-Apache) identified problem :-(
>
> -- 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
>
Re: After Apache front-end: no log in, no trail
Posted by Mariano Rico <ma...@uam.es>.
Hi Florian,
> deciding for one "entry point" and configuring this the baseURL is the way
> to go.
>
Have you had this running? With login? Please, tell me how... :-)
> BTW, any reason against using mod_proxy_ajp?
>
>
I tried that at first, but it produced an error. It seems to be a versions
incompatibility (Tomcat-Apache) identified problem :-(
-- 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
Re: After Apache front-end: no log in, no trail
Posted by Florian Holeczek <fl...@holeczek.de>.
Hi Mariano,
deciding for one "entry point" and configuring this the baseURL is the way to go.
BTW, any reason against using mod_proxy_ajp?
Regards
Florian
----- Ursprüngliche Mail -----
Von: "Mariano Rico" <ma...@gmail.com>
An: jspwiki-dev@incubator.apache.org
Gesendet: Montag, 5. März 2012 17:08:34
Betreff: After Apache front-end: no log in, no trail
Hi all,
I installed JSPWiki 2.8.4 in my machine (asera.ii.uam.es:8080/DBpediaES),
and everything was perfect.
However, when I did set up Apache (v 2.2) as front-end (with ProxyPass and
proxyPassReverse) pointing to this wiki, the log in mechanism disappeared.
I can not log in, but I get no errors in the log, and the "Your trail:" is
not working (it is emptly).
I had to change the BaseURL to es.dbpedia.org, what results in a "no css"
version running at asera.ii.uam.es:8080/DBpediaES but a good presentation
for es.dbpedia.org ¿Is this the usual way? I thought that the Apache
front-end should not modify the behavior of JSPWiki, ans I could use both
"instances".
¿Any suggestion?
Best regards,
-Mariano