hello, This happens because of the previously persisted configurations in file system. Please see the jira for information.
Thank you. On Thu, Feb 27, 2014 at 2:20 AM, Rajika Kumarasiri < rajika.kumaras...@gmail.com> wrote: > hello Sergio, > > Thank you for your answers. I haven't installed Marmotta before. I cleared > the browser cache. Still the issue is there. Below is the curl out put. > > [rajika@localhost marmotta-webapp]$ curl -I http://localhost:8080/ > HTTP/1.1 302 Found > Server: Apache Marmotta/3.2.0-SNAPSHOT (build 2+) > Set-Cookie: JSESSIONID=1E8A4E4AEC0D54C8ADBD56CB358380BE; Path=/; HttpOnly > Location: http://localhost.localdomain:8080/marmotta/core/admin/about.html > Content-Type: text/html;charset=ISO-8859-1 > Content-Length: 0 > Date: Thu, 27 Feb 2014 06:59:42 GMT > > As you can see there is a http re-direct returned by the server. I have > created a jira for the issue > https://issues.apache.org/jira/browse/MARMOTTA-447. > > Thank you. > > > > > On Wed, Feb 26, 2014 at 6:38 AM, Sergio Fernández < > sergio.fernan...@salzburgresearch.at> wrote: > >> Hi, >> >> >> On 26/02/14 08:55, Rajika Kumarasiri wrote: >> >>> Actually I wanted to tell you, when I tried on Fedora(using Google >>> Chrome) >>> the context root http://localhost:8080/ was re-directed to >>> http://localhost:8080/marmotta/core/admin/about.html page which I ended >>> up >>> with a 404. But when I built the war on Windows the embedded tomcat >>> version >>> works fine. >>> >> >> That's strange, because Linux is one our main development/testing >> environments; not Fedora, but Debian/Ubuntu. >> >> Have you installed and access Marmotta there before? Because recently I'm >> seeing how browsers are heavily catching redirects. And it could be your >> Chrome is behaving in that way. >> >> Try with something more basic, like: >> >> curl -I http://localhost:8080/ >> >> By default the embedded tomcat should redirect to ; >> >> http://localhost:8080/core/admin/about.html >> >> You can see (and customize) those settings in the pom.xml properties. >> >> >> I built the war and deployed into a separate tomcat instance on Fedora >>> and >>> it works. I just wanted to tell you here because I am not sure if there >>> is >>> a possible bug. >>> >> >> It should not make any different. Beside the caching issue I commented >> above. >> >> Please, confirm it, and if not file a bug in jira, please. >> >> >> Cheers, >> >> -- >> Sergio Fernández >> Senior Researcher >> Knowledge and Media Technologies >> Salzburg Research Forschungsgesellschaft mbH >> Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria >> T: +43 662 2288 318 | M: +43 660 2747 925 >> sergio.fernan...@salzburgresearch.at >> http://www.salzburgresearch.at >> > >
