Mixing Static and Dynamic Contents

a.afzali2003 · 2016-11-06T20:03:52+00:00

try to iterate on loginpagematch with for:for loginpagematch in ngx.re.gmatch(body, "" .. htmlvaluetomakeem...

Mixing Static and Dynamic Contents

a.afzali2003

Hi Folks,
This is a newbie here. I am struggling to a combination of static and dynamic contents for a Login page. In this scenario I have html, js and css files to serve loading the page. At the same time I have a lua script to handle submit action. In nginx config file I have a location section as follows:

location / {
    rewrite ^/$    /login permanent;
    default_type text/html;
    root /opt/sso;

    content_by_lua_file /opt/sso/server.lua;
}

My problem is I could not manage to have both mechanisms at the same time! Is it possible to separate static and dynamic sections by HTTP methods? (static for GET and dynamic for POST method).

Appreciate all comments.

Afshin

rpaprocki

Hi,

On Sun, Nov 6, 2016 at 4:03 AM, afshin afzali <a.afz...@gmail.com> wrote:

Hi Folks,
This is a newbie here. I am struggling to a combination of static and dynamic contents for a Login page. In this scenario I have html, js and css files to serve loading the page. At the same time I have a lua script to handle submit action. In nginx config file I have a location section as follows:

location / {
    rewrite ^/$    /login permanent;
    default_type text/html;
    root /opt/sso;

    content_by_lua_file /opt/sso/server.lua;
}

My problem is I could not manage to have both mechanisms at the same time! Is it possible to separate static and dynamic sections by HTTP methods? (static for GET and dynamic for POST method).

Only one content phase handler can exist per location. What you may want to do is use a templating engine such as https://github.com/bungle/lua-resty-template to build the HTML response based on the request content, essentially turning each request into a 'dynamic' response (but your template can include plain HTML with no variable interpolation for some requests). From there it would probably make sense to design your site's asset layout such that js/css/etc are server from a separate directory or location, and can just be served via Nginx.

You would not be able to handle different methods in the Nginx config, but you could handle all of this in a content_by_lua handler using something like https://github.com/APItools/router.lua (I believe bungle mentioned he may also be working on a fleshed-out router for OpenResty projects as well).

Another alternative would be to have the login page post to a different URI, so that you have separate location blocks (and content handlers) for your static and dynamic content.

Good luck with it!

a.afzali2003

Hi Robert,

Many thanks for the complete response. After I made this post I noticed the template engines solution. I am on that way now and I know it's right. Really appreciated.

Afshin

On Mon, Nov 7, 2016 at 6:28 PM Robert Paprocki <rpap...@fearnothingproductions.net> wrote:

Hi,

On Sun, Nov 6, 2016 at 4:03 AM, afshin afzali <a.afz...@gmail.com> wrote:
Hi Folks,
This is a newbie here. I am struggling to a combination of static and dynamic contents for a Login page. In this scenario I have html, js and css files to serve loading the page. At the same time I have a lua script to handle submit action. In nginx config file I have a location section as follows:

location / {
    rewrite ^/$    /login permanent;
    default_type text/html;
    root /opt/sso;

    content_by_lua_file /opt/sso/server.lua;
}

My problem is I could not manage to have both mechanisms at the same time! Is it possible to separate static and dynamic sections by HTTP methods? (static for GET and dynamic for POST method).

Only one content phase handler can exist per location. What you may want to do is use a templating engine such as https://github.com/bungle/lua-resty-template to build the HTML response based on the request content, essentially turning each request into a 'dynamic' response (but your template can include plain HTML with no variable interpolation for some requests). From there it would probably make sense to design your site's asset layout such that js/css/etc are server from a separate directory or location, and can just be served via Nginx.

You would not be able to handle different methods in the Nginx config, but you could handle all of this in a content_by_lua handler using something like https://github.com/APItools/router.lua (I believe bungle mentioned he may also be working on a fleshed-out router for OpenResty projects as well).

Another alternative would be to have the login page post to a different URI, so that you have separate location blocks (and content handlers) for your static and dynamic content.

Good luck with it!

--
.