[opencms-dev] Problem with nginx opencms workplace configuration

Marc Johnson originalstoic at yahoo.com
Mon Sep 9 17:44:58 CEST 2013


Yup, I had been thinking that while waiting for replies here and you got it  exactly right.  

It was easy.  My problem is that I'm not that great at nginx rewrite rules.  For everyone's edification I just added the line below after my main location block(location / {    proxy_redirect          off; etc...)

    location /opencms { 
            rewrite ^/opencms/(.*)$ /$1; 
    }





________________________________
 From: Stephan Hartmann <hartmann at metamesh.de>
To: Marc Johnson <originalstoic at yahoo.com>; The OpenCms mailing list <opencms-dev at opencms.org> 
Sent: Monday, September 9, 2013 5:47 AM
Subject: Re: [opencms-dev] Problem with nginx opencms workplace configuration
 


Hi Marc,

I guess you have to add a location for "/opencms" to be passed to http://127.0.0.1:8081/opencms/ as well or prevent in some other way that requests that already point to the opencms servlet become prefixed with another "/opencms" again.


Regards,

Stephan





2013/9/7 Marc Johnson <originalstoic at yahoo.com>

The workplace is working generally except the popup boxes(gallery, vfs file paths, in admin... the Group box, etc ...) within the workspace are throwing errors.
>
>for example if I click the box in User Administration to create a new Group and then go to select a Parent Group, I get vfs resource not found with the requisite stack trace.  
>
>Upon further investigation in the code I see that a js function is called:
>
>"javascript:openGroupWin('/opencms/system/workplace/commons/group_selection.jsp','EDITOR',  'parentGroup.0', document, null, null, '');"
>
>Clearly the problem is that the /opencms/ on the front end is not getting stripped out when the popup happens.  Sure enough when I remove the opencms and do just mydomain.com/system...(path from above), the correct working workplace page is rendered.  This is what's happening in every other case so the workplace is quite functional.
>
>So... can anybody say why nginx is handling this everywhere else in the workplace but not for these popups.  Has anyone seen this before?  My nginx settings are below.
>
>server {
>    listen 83;
>    #server_name mydomain.com;
>    listen [::]:83 default_server ipv6only=on;
>    root /usr/share/tomcat7/webapps/ROOT/;
>    index index.html index.htm index.jsp;
>
>    # Make site accessible from http://localhost/
>    server_name localhost;
>
>    location / {    
>        proxy_redirect          off;
>              
 proxy_pass              http://127.0.0.1:8081/opencms/;
>            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; 
>    }
>
>    location /export {
>        try_files $uri /handle404?exporturi=$uri&$args;
>        expires       24h;
>        add_header    Cache-Control  private;
>   
 }
>
>    location /external {
>        expires       24h;
>        add_header    Cache-Control  private;
>    }
>
>    location /resources {
>        expires       24h;
>        add_header    Cache-Control  private;
>    }
>}
>
>_______________________________________________
>This mail is sent to you from the opencms-dev mailing list
>To change your list options, or to unsubscribe from the list, please visit
>http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20130909/c304c6b9/attachment.htm>


More information about the opencms-dev mailing list