Re: [xwiki-users] Tomcat error 500 for pages with in title
small update: actually StackExchange has the solution: http://serverfault.com/questions/459369/disabling-url-decoding-in-nginx-proxy On 04/24/2015 10:16 AM, Clemens Klein-Robbenhaar wrote: We are getting closer to a solution ;) I am pretty sure that if you get the error via nginx, and nginx shows in the access log something like : GET /xwiki/wiki/hardware/view/Test/Test+with+%22quotation%22 HTTP/1.1 then in turn the tomcat acess will show for the same request: GET /xwiki/wiki/hardware/view/Test/Test+with+quotation HTTP/1.1 and that ... will not end well. I had a similar problem with apache which decodes the url partially before sending it to the backend server. The fix was to send the original url to the backend, as explained in http://dracos.co.uk/code/apache-rewrite-problem/ Unfortunately I have no idea if/how ngninx handles this problem. Can you post the relevant part of your nginx configuration anyway, so anyone with better knowledge of nginx might figure out what to do? Clemens I have to take back that it can be reproduced with tomcat directly because meanwhile I can't anymore, now it works, strange. But calling the page via nginx still produces the error. Tomcat log shows the following entry for the URL when opened from the tomcat URL: [24/Apr/2015:09:18:45 +0200] GET /xwiki/wiki/hardware/view/Test/Test+with+%22quotation%22 HTTP/1.1 200 41185 Nginx shows the following for the 500 error: [24/Apr/2015:09:15:56 +0200] GET /xwiki/wiki/hardware/view/Test/Test+with+%22quotation%22 HTTP/1.1 500 8831 - Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0 Can somebody advise me how to make Nginx behave? 2015-04-23 16:42 GMT+02:00 Clemens Klein-Robbenhaar c.robbenh...@espresto.com: I once had quite bad problems when having an apache in between who internally decoded an URI and then encoded it back, but only barely ... However it seems this is ruled out here, if the problem happens with tomcat, too. How do you reproduce the issue with tomcat directly? a) if you directly *call* a page with an '' in the URL then I'd say, the error is ok, the URL should have been encoded. b) however if you first go e.g. to the wiki start page, and then navigate to the page with quotes in the names, then XWiki should encode the url properly, and this error should not happen ... Can you see what tomcat writes in its access log for that page? Can you check in the generated HTML of a link that the '' is actually encoded as '%22 in the href attribute? (Actually this must be the case as otherwise the quote would just terminate the href, at least in these cases where double quotes as attribute delimiters rare used. ) On 04/23/2015 04:30 PM, D R wrote: Thanks for the feedback. Yes, there is an Nginx as frontend running, but I also can reproduce the issue by calling the direct tomcat address. I don't know what could be wrong because I'm no tomcat expert at all. 2015-04-23 13:10 GMT+02:00 Clemens Klein-Robbenhaar c.robbenh...@espresto.com: I installed tomcat8 as apache-tomcat-8.0.21, and java as jdk1.8.0_45 and cannot reproduce this either, at least not directly. After I create a page with name `Page with quotes`, I cannot trigger the problem in the browser, but of course I can do so manually by feeding in a wrong URL: i.e.: curl ' http://localhost:8080/xwiki/bin/view/Sandbox/Page+with+%22quotes%22' just downloads the page (quotes properly encoded) curl 'http://localhost:8080/xwiki/bin/view/Sandbox/Page+with+ quotes' produces error page (actually from XWiki, I wonder why tomcat does not already sends a 400 ...) However when I look into the links that XWiki creates, I see they are all properly URL-encoded (with %22 for the ''), so no issue here Is there anything else in the setup? For example an apache as frontand or the like? Clemens On 04/22/2015 12:43 PM, D R wrote: Hi, it has nothing to do with the space name. I can reproduce the issue accross several (sub-)wikis and different spaces. The only thing relevant to reproduce the error is the quotation mark () in the page name. As soon as I want to open such a document or create one I get the 500 error from tomcat mentioned below. Yes, the Windows server accepts the quotation marks, I can click the document links and they are shown correctly, the Ubuntu Server throughs the 500 error at me. Regs, Dennis 2015-04-22 11:44 GMT+02:00 ricardo.julio.rodriguez.fernan...@sergas.es : Hi D R! Does this URL included in the error message some special meaning for you? Could it be the only space with some reserved characters in the space name? http://10.80.75.216/xwiki/wiki/kunden/view/Some++Space/Kunden+Appstore+iPad+Apps Perhaps they were allowed in your Windows Server and Ubuntu rejects them? Cheers! -- Ricardo Rodríguez Research Management and Promotion Technician Technical
Re: [xwiki-users] Tomcat error 500 for pages with in title
That did the trick, thanks.
Originally I took the config from
http://platform.xwiki.org/xwiki/bin/view/AdminGuide/NginX and edited it to
my needs.
No I changed nginx config to:
location / {
proxy_passhttp://localhost:8080;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $http_host;
proxy_set_header X-Forwarded-Proto $scheme;
expires 0m;
}
And it works.
Many thanks!
2015-04-24 10:29 GMT+02:00 Clemens Klein-Robbenhaar
c.robbenh...@espresto.com:
small update: actually StackExchange has the solution:
http://serverfault.com/questions/459369/disabling-url-decoding-in-nginx-proxy
On 04/24/2015 10:16 AM, Clemens Klein-Robbenhaar wrote:
We are getting closer to a solution ;)
I am pretty sure that if you get the error via nginx, and nginx shows in
the
access log something like :
GET /xwiki/wiki/hardware/view/Test/Test+with+%22quotation%22 HTTP/1.1
then in turn the tomcat acess will show for the same request:
GET /xwiki/wiki/hardware/view/Test/Test+with+quotation HTTP/1.1
and that ... will not end well.
I had a similar problem with apache which decodes the url partially
before sending it to the backend server. The fix was to send the
original url to the backend, as explained in
http://dracos.co.uk/code/apache-rewrite-problem/
Unfortunately I have no idea if/how ngninx handles this problem.
Can you post the relevant part of your nginx configuration anyway,
so anyone with better knowledge of nginx might figure out what to do?
Clemens
I have to take back that it can be reproduced with tomcat directly
because
meanwhile I can't anymore, now it works, strange. But calling the page
via
nginx still produces the error.
Tomcat log shows the following entry for the URL when opened from the
tomcat URL:
[24/Apr/2015:09:18:45 +0200] GET
/xwiki/wiki/hardware/view/Test/Test+with+%22quotation%22 HTTP/1.1 200
41185
Nginx shows the following for the 500 error:
[24/Apr/2015:09:15:56 +0200] GET
/xwiki/wiki/hardware/view/Test/Test+with+%22quotation%22 HTTP/1.1 500
8831
- Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101
Firefox/37.0
Can somebody advise me how to make Nginx behave?
2015-04-23 16:42 GMT+02:00 Clemens Klein-Robbenhaar
c.robbenh...@espresto.com:
I once had quite bad problems when having an apache in between
who internally decoded an URI and then encoded it back, but only
barely
...
However it seems this is ruled out here, if the problem happens with
tomcat, too.
How do you reproduce the issue with tomcat directly?
a) if you directly *call* a page with an '' in the URL
then I'd say, the error is ok, the URL should have been encoded.
b) however if you first go e.g. to the wiki start page,
and then navigate to the page with quotes in the names, then
XWiki should encode the url properly, and this error should not
happen
...
Can you see what tomcat writes in its access log for that page?
Can you check in the generated HTML of a link that the ''
is actually encoded as '%22 in the href attribute? (Actually
this must be the case as otherwise the quote would just terminate the
href,
at least in these cases where double quotes as attribute delimiters
rare
used. )
On 04/23/2015 04:30 PM, D R wrote:
Thanks for the feedback.
Yes, there is an Nginx as frontend running, but I also can reproduce
the
issue by calling the direct tomcat address.
I don't know what could be wrong because I'm no tomcat expert at all.
2015-04-23 13:10 GMT+02:00 Clemens Klein-Robbenhaar
c.robbenh...@espresto.com:
I installed tomcat8 as apache-tomcat-8.0.21, and java as jdk1.8.0_45
and cannot reproduce this either, at least not directly.
After I create a page with name `Page with quotes`,
I cannot trigger the problem in the browser, but of course I can do
so
manually
by feeding in a wrong URL:
i.e.:
curl '
http://localhost:8080/xwiki/bin/view/Sandbox/Page+with+%22quotes%22'
just downloads the page (quotes properly encoded)
curl 'http://localhost:8080/xwiki/bin/view/Sandbox/Page+with+
quotes'
produces error page (actually from XWiki, I wonder why tomcat does
not
already
sends a 400 ...)
However when I look into the links that XWiki creates, I see they are
all
properly URL-encoded (with %22 for the ''), so no issue here
Is there anything else in the setup? For example an apache as
frontand
or
the like?
Clemens
On 04/22/2015 12:43 PM, D R wrote:
Hi,
it has nothing to do with the space name. I can reproduce the issue
accross
several (sub-)wikis and different spaces. The only thing relevant to
reproduce the error is the quotation mark () in the page name.
As soon as I want to open such a document or create one I get the
500
error
from tomcat mentioned below.
Yes, the
Re: [xwiki-users] Tomcat error 500 for pages with in title
We are getting closer to a solution ;) I am pretty sure that if you get the error via nginx, and nginx shows in the access log something like : GET /xwiki/wiki/hardware/view/Test/Test+with+%22quotation%22 HTTP/1.1 then in turn the tomcat acess will show for the same request: GET /xwiki/wiki/hardware/view/Test/Test+with+quotation HTTP/1.1 and that ... will not end well. I had a similar problem with apache which decodes the url partially before sending it to the backend server. The fix was to send the original url to the backend, as explained in http://dracos.co.uk/code/apache-rewrite-problem/ Unfortunately I have no idea if/how ngninx handles this problem. Can you post the relevant part of your nginx configuration anyway, so anyone with better knowledge of nginx might figure out what to do? Clemens I have to take back that it can be reproduced with tomcat directly because meanwhile I can't anymore, now it works, strange. But calling the page via nginx still produces the error. Tomcat log shows the following entry for the URL when opened from the tomcat URL: [24/Apr/2015:09:18:45 +0200] GET /xwiki/wiki/hardware/view/Test/Test+with+%22quotation%22 HTTP/1.1 200 41185 Nginx shows the following for the 500 error: [24/Apr/2015:09:15:56 +0200] GET /xwiki/wiki/hardware/view/Test/Test+with+%22quotation%22 HTTP/1.1 500 8831 - Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0 Can somebody advise me how to make Nginx behave? 2015-04-23 16:42 GMT+02:00 Clemens Klein-Robbenhaar c.robbenh...@espresto.com: I once had quite bad problems when having an apache in between who internally decoded an URI and then encoded it back, but only barely ... However it seems this is ruled out here, if the problem happens with tomcat, too. How do you reproduce the issue with tomcat directly? a) if you directly *call* a page with an '' in the URL then I'd say, the error is ok, the URL should have been encoded. b) however if you first go e.g. to the wiki start page, and then navigate to the page with quotes in the names, then XWiki should encode the url properly, and this error should not happen ... Can you see what tomcat writes in its access log for that page? Can you check in the generated HTML of a link that the '' is actually encoded as '%22 in the href attribute? (Actually this must be the case as otherwise the quote would just terminate the href, at least in these cases where double quotes as attribute delimiters rare used. ) On 04/23/2015 04:30 PM, D R wrote: Thanks for the feedback. Yes, there is an Nginx as frontend running, but I also can reproduce the issue by calling the direct tomcat address. I don't know what could be wrong because I'm no tomcat expert at all. 2015-04-23 13:10 GMT+02:00 Clemens Klein-Robbenhaar c.robbenh...@espresto.com: I installed tomcat8 as apache-tomcat-8.0.21, and java as jdk1.8.0_45 and cannot reproduce this either, at least not directly. After I create a page with name `Page with quotes`, I cannot trigger the problem in the browser, but of course I can do so manually by feeding in a wrong URL: i.e.: curl ' http://localhost:8080/xwiki/bin/view/Sandbox/Page+with+%22quotes%22' just downloads the page (quotes properly encoded) curl 'http://localhost:8080/xwiki/bin/view/Sandbox/Page+with+ quotes' produces error page (actually from XWiki, I wonder why tomcat does not already sends a 400 ...) However when I look into the links that XWiki creates, I see they are all properly URL-encoded (with %22 for the ''), so no issue here Is there anything else in the setup? For example an apache as frontand or the like? Clemens On 04/22/2015 12:43 PM, D R wrote: Hi, it has nothing to do with the space name. I can reproduce the issue accross several (sub-)wikis and different spaces. The only thing relevant to reproduce the error is the quotation mark () in the page name. As soon as I want to open such a document or create one I get the 500 error from tomcat mentioned below. Yes, the Windows server accepts the quotation marks, I can click the document links and they are shown correctly, the Ubuntu Server throughs the 500 error at me. Regs, Dennis 2015-04-22 11:44 GMT+02:00 ricardo.julio.rodriguez.fernan...@sergas.es : Hi D R! Does this URL included in the error message some special meaning for you? Could it be the only space with some reserved characters in the space name? http://10.80.75.216/xwiki/wiki/kunden/view/Some++Space/Kunden+Appstore+iPad+Apps Perhaps they were allowed in your Windows Server and Ubuntu rejects them? Cheers! -- Ricardo Rodríguez Research Management and Promotion Technician Technical Secretariat Health Research Institute of Santiago de Compostela (IDIS) http://www.idisantiago.es De: users [users-boun...@xwiki.org] en nombre de D R [ rir@gmail.com ]
Re: [xwiki-users] Tomcat error 500 for pages with in title
Hi guys,
On 24 Apr 2015 at 13:01:25, D R (rir@gmail.com(mailto:rir@gmail.com))
wrote:
That did the trick, thanks.
Originally I took the config from
http://platform.xwiki.org/xwiki/bin/view/AdminGuide/NginX and edited it to
my needs.
If http://platform.xwiki.org/xwiki/bin/view/AdminGuide/NginX is not correct or
needs to be updated, please make the required modifications on that page so
that it helps the next person :)
Thanks a lot
-Vincent
No I changed nginx config to:
location / {
proxy_passhttp://localhost:8080;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $http_host;
proxy_set_header X-Forwarded-Proto $scheme;
expires 0m;
}
And it works.
Many thanks!
2015-04-24 10:29 GMT+02:00 Clemens Klein-Robbenhaar
c.robbenh...@espresto.com:
small update: actually StackExchange has the solution:
http://serverfault.com/questions/459369/disabling-url-decoding-in-nginx-proxy
On 04/24/2015 10:16 AM, Clemens Klein-Robbenhaar wrote:
We are getting closer to a solution ;)
I am pretty sure that if you get the error via nginx, and nginx shows in
the
access log something like :
GET /xwiki/wiki/hardware/view/Test/Test+with+%22quotation%22 HTTP/1.1
then in turn the tomcat acess will show for the same request:
GET /xwiki/wiki/hardware/view/Test/Test+with+quotation HTTP/1.1
and that ... will not end well.
I had a similar problem with apache which decodes the url partially
before sending it to the backend server. The fix was to send the
original url to the backend, as explained in
http://dracos.co.uk/code/apache-rewrite-problem/
Unfortunately I have no idea if/how ngninx handles this problem.
Can you post the relevant part of your nginx configuration anyway,
so anyone with better knowledge of nginx might figure out what to do?
Clemens
I have to take back that it can be reproduced with tomcat directly
because
meanwhile I can't anymore, now it works, strange. But calling the page
via
nginx still produces the error.
Tomcat log shows the following entry for the URL when opened from the
tomcat URL:
[24/Apr/2015:09:18:45 +0200] GET
/xwiki/wiki/hardware/view/Test/Test+with+%22quotation%22 HTTP/1.1 200
41185
Nginx shows the following for the 500 error:
[24/Apr/2015:09:15:56 +0200] GET
/xwiki/wiki/hardware/view/Test/Test+with+%22quotation%22 HTTP/1.1 500
8831
- Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101
Firefox/37.0
Can somebody advise me how to make Nginx behave?
2015-04-23 16:42 GMT+02:00 Clemens Klein-Robbenhaar
c.robbenh...@espresto.com:
I once had quite bad problems when having an apache in between
who internally decoded an URI and then encoded it back, but only
barely
...
However it seems this is ruled out here, if the problem happens with
tomcat, too.
How do you reproduce the issue with tomcat directly?
a) if you directly *call* a page with an '' in the URL
then I'd say, the error is ok, the URL should have been encoded.
b) however if you first go e.g. to the wiki start page,
and then navigate to the page with quotes in the names, then
XWiki should encode the url properly, and this error should not
happen
...
Can you see what tomcat writes in its access log for that page?
Can you check in the generated HTML of a link that the ''
is actually encoded as '%22 in the href attribute? (Actually
this must be the case as otherwise the quote would just terminate the
href,
at least in these cases where double quotes as attribute delimiters
rare
used. )
On 04/23/2015 04:30 PM, D R wrote:
Thanks for the feedback.
Yes, there is an Nginx as frontend running, but I also can reproduce
the
issue by calling the direct tomcat address.
I don't know what could be wrong because I'm no tomcat expert at all.
2015-04-23 13:10 GMT+02:00 Clemens Klein-Robbenhaar
c.robbenh...@espresto.com:
I installed tomcat8 as apache-tomcat-8.0.21, and java as jdk1.8.0_45
and cannot reproduce this either, at least not directly.
After I create a page with name `Page with quotes`,
I cannot trigger the problem in the browser, but of course I can do
so
manually
by feeding in a wrong URL:
i.e.:
curl '
http://localhost:8080/xwiki/bin/view/Sandbox/Page+with+%22quotes%22'
just downloads the page (quotes properly encoded)
curl 'http://localhost:8080/xwiki/bin/view/Sandbox/Page+with+
quotes'
produces error page (actually from XWiki, I wonder why tomcat does
not
already
sends a 400 ...)
However when I look into the links that XWiki creates, I see they are
all
properly URL-encoded (with %22 for the ''), so no issue here
Is there anything else in the setup?
Re: [xwiki-users] Clear them all! :p
Hello, Ok... I rolled back my wiki to 1.1 version and now... I can't administrate XWiki. I haven't options to change something. It's what I said (XWiki is difficult for no computer users). Deleting or rollback is easy but restore last settings is quite hard. I've lost half of spaces while I've been trying to make a backup. Now i can't import this back up files... I have nothing ;) Please don't compare me with XWiki rebel :p XWiki is a great tool but you know... Greetings, Maciek. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] Multipage PDF
Hello, I've installed XWiki Multipage PDF Export and now.. why all hyperlinks transport me to the my XWiki page online? I would like to export my all SPACE to PDF but as I said.. I need all contain, not just links ;) Greetings, Maciek. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] How to Add WYSIWIG toolbar button
Hi
I have a problem where users want to highlight text in the WYSIWIG editor and
press a button on the toolbar to automatically add the {{code}}, {{warning}}
etc. start and end tags to the text. I know how to add a macro button and to
style it. But the problem with the macro is that it pops up a form with a text
area that you then need to fill in with text you want to put inside the tags.
The behaviour I am looking for is similar to highlighting text and then
pressing the Bold button on the toolbar.
I have done some digging/searching/googling and found the simpledittoolbar.vm
and I’ve customised this and added the copy to my skin. I have added the
following code in the relevant sections and it works perfectly when I click
EditWiki but it doesn’t show on the toolbar when I click EditWYSIWIG. I am
running XWiki 7.0
#set($discard = $syntax10Elements.add(['code', '{{code}}', '{{/code}}',
'page_code']))
#set($discard = $syntax20Elements.add(['code', '{{code}}', '{{/code}}',
'page_code']))
#set($discard = $confluence10Elements.add(['code', '{{code}}', '{{/code}}',
'page_code']))
So any idea how I can make the button show on the WYSIWIG toolbar?
Alternatively how do I make the macro execute on the highlighted text?
Thanks in advance.
Kind regards,
Mahomed
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] Solution to upgrade a farm (Re: V7, wikis creation, descriptors and wizard issues.)
Hi Marius/Thomas/Denis/All, I agree that Martin’s use case is valid (we discussed it on IRC a few days ago and Denis confirmed the need that he’s seen). Here’s the need: - You have farm 1 on XWiki version N with several users/customers on it each with a subwiki - You want to upgrade some of them to a more recent version of XWiki - You install farm 2 with XWiki version P (where P N) - Thus the need is: how to move subwiki S from farm 1 to farm 2 I think we need to recommend some solution for this typical use case and document it at http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Upgrade. This page currently doesn’t mention anything about a farm/subwikis. Do we have some official recommendation on this (best practice)? Do we know how to support this use case? If not, is there something we can do make this use case simpler to achieve? Thanks -Vincent On 24 Apr 2015 at 07:48:33, Marius Dumitru Florea (mariusdumitru.flo...@xwiki.com(mailto:mariusdumitru.flo...@xwiki.com)) wrote: On Thu, Apr 23, 2015 at 1:49 PM, m...@ow2.org wrote: Le 21/04/2015 17:10, m...@ow2.org a écrit : Why : the issue at this point is there is no folder in the PermDir/jobs/status/distribution/wiki/ which sounds logical because we created the descriptor by hand throught a XAR import which doesn't include the process of writing initial status.xml files in PermDir/jobs/status/distribution/wiki//status.xml So indeed we're stuck. How do we run the Document Wizard Upgrade at this point ? The other issue was the imported wiki skin definition was overriding the DW URL. Since then we have moved to XWiki 6.4.4 as it is the version supported by XWiki SAS. We did the wizard trick and poped up the DW by typing the URL by hand in the broswer, so it bypass the skin. I recommend switching temporarily to the default skin before doing an upgrade. Anyway, there is still some migration/move/upgrade use cases scenarios to elaborate. I'll start this when I got time. But anyone can start over, maybe you, Denis ? -- Martin ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Tomcat error 500 for pages with in title
I have to take back that it can be reproduced with tomcat directly because meanwhile I can't anymore, now it works, strange. But calling the page via nginx still produces the error. Tomcat log shows the following entry for the URL when opened from the tomcat URL: [24/Apr/2015:09:18:45 +0200] GET /xwiki/wiki/hardware/view/Test/Test+with+%22quotation%22 HTTP/1.1 200 41185 Nginx shows the following for the 500 error: [24/Apr/2015:09:15:56 +0200] GET /xwiki/wiki/hardware/view/Test/Test+with+%22quotation%22 HTTP/1.1 500 8831 - Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0 Can somebody advise me how to make Nginx behave? 2015-04-23 16:42 GMT+02:00 Clemens Klein-Robbenhaar c.robbenh...@espresto.com: I once had quite bad problems when having an apache in between who internally decoded an URI and then encoded it back, but only barely ... However it seems this is ruled out here, if the problem happens with tomcat, too. How do you reproduce the issue with tomcat directly? a) if you directly *call* a page with an '' in the URL then I'd say, the error is ok, the URL should have been encoded. b) however if you first go e.g. to the wiki start page, and then navigate to the page with quotes in the names, then XWiki should encode the url properly, and this error should not happen ... Can you see what tomcat writes in its access log for that page? Can you check in the generated HTML of a link that the '' is actually encoded as '%22 in the href attribute? (Actually this must be the case as otherwise the quote would just terminate the href, at least in these cases where double quotes as attribute delimiters rare used. ) On 04/23/2015 04:30 PM, D R wrote: Thanks for the feedback. Yes, there is an Nginx as frontend running, but I also can reproduce the issue by calling the direct tomcat address. I don't know what could be wrong because I'm no tomcat expert at all. 2015-04-23 13:10 GMT+02:00 Clemens Klein-Robbenhaar c.robbenh...@espresto.com: I installed tomcat8 as apache-tomcat-8.0.21, and java as jdk1.8.0_45 and cannot reproduce this either, at least not directly. After I create a page with name `Page with quotes`, I cannot trigger the problem in the browser, but of course I can do so manually by feeding in a wrong URL: i.e.: curl ' http://localhost:8080/xwiki/bin/view/Sandbox/Page+with+%22quotes%22' just downloads the page (quotes properly encoded) curl 'http://localhost:8080/xwiki/bin/view/Sandbox/Page+with+ quotes' produces error page (actually from XWiki, I wonder why tomcat does not already sends a 400 ...) However when I look into the links that XWiki creates, I see they are all properly URL-encoded (with %22 for the ''), so no issue here Is there anything else in the setup? For example an apache as frontand or the like? Clemens On 04/22/2015 12:43 PM, D R wrote: Hi, it has nothing to do with the space name. I can reproduce the issue accross several (sub-)wikis and different spaces. The only thing relevant to reproduce the error is the quotation mark () in the page name. As soon as I want to open such a document or create one I get the 500 error from tomcat mentioned below. Yes, the Windows server accepts the quotation marks, I can click the document links and they are shown correctly, the Ubuntu Server throughs the 500 error at me. Regs, Dennis 2015-04-22 11:44 GMT+02:00 ricardo.julio.rodriguez.fernan...@sergas.es : Hi D R! Does this URL included in the error message some special meaning for you? Could it be the only space with some reserved characters in the space name? http://10.80.75.216/xwiki/wiki/kunden/view/Some++Space/Kunden+Appstore+iPad+Apps Perhaps they were allowed in your Windows Server and Ubuntu rejects them? Cheers! -- Ricardo Rodríguez Research Management and Promotion Technician Technical Secretariat Health Research Institute of Santiago de Compostela (IDIS) http://www.idisantiago.es De: users [users-boun...@xwiki.org] en nombre de D R [ rir@gmail.com ] Enviado: miércoles, 22 de abril de 2015 11:33 Para: XWiki Users Asunto: Re: [xwiki-users] Tomcat error 500 for pages with in title Does anybody have additional hints how I can solve this blocking issue? Thanks in advance. 2015-04-21 9:56 GMT+02:00 D R rir@gmail.com: Thanks, Ricardo. I checked the encoding documentation and performed some steps but the issue still occurs. What I did: - XWiki encoding - web.xml: already UTF-8 - xwiki.cfg: already UTF-8 - HTML encoding: added to each wiki (Content-Type tag was completely missing) - Hibernate configuration: UTF-8 properties added - MySQL config: added UTF-8 settings and converted each database from utf8_general_ci to utf8_bin -
