<div dir="ltr">And an idea, maybe you can add a time based access control in nginx rather than IP.<br>for example , some admin pages can only access at work time.<br><br><div class="gmail_quote">2008/7/25 pf shineyear <<a href="mailto:shinepf@gmail.com">shinepf@gmail.com</a>>:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">u can use a function "ngx_time()" it return a time_t int about seconds<br>
since 1/1/1970<br>
<div><div></div><div class="Wj3C7c"><br>
On Fri, Jul 25, 2008 at 3:59 AM, Mike Harding <<a href="mailto:mvh@ix.netcom.com">mvh@ix.netcom.com</a>> wrote:<br>
> I am porting some apache rewrite rules that use the TIME variable (just<br>
> unix epoch, seconds since 1/1/1970). What would be my best option for<br>
> nginx?<br>
><br>
> I could<br>
><br>
> - modify the code to provide a $time variable<br>
> - use fgci<br>
> - use the embedded perl option<br>
> - proxy to an apache server<br>
><br>
> any other options? How much work would be involved with the first<br>
> option? I am an accomplished C programmer and could provide patches<br>
> back to the project...<br>
><br>
> - Mike H.<br>
><br>
><br>
><br>
><br>
<br>
</div></div></blockquote></div><br></div>