I agree. That is not the right way to design a website.
What about portable website development anyway?
Lean website design works for me and the websites that we design look great
on virtually any interface. They are not gaudy though and do not feature a
bunch of flashy details.
Lean and clean.
On 12 Aug 2013 19:52, "Rodrigo Serra Inacio" wrote:
>
> Hi,
> What do you think is more efficient...cookies or redirect by the user
agent ?
If you do it based on UA *at*the*network*border* you'll block mobile users
from switching to your desktop site if they really want to. I /hate/ sites
that do
Hi,
I'm writing a filter module which implies a backend to be sending XML with
information about files that have to be concatenated and sent to the
client.
One way to send a file is to `ngx_read_file` into a buffer allocated in the
heap(pool) and push it onto the chain. However, I obviously can't
Hi,
What do you think is more efficient...cookies or redirect by the user agent
?
Thank you
2013/8/12 Adie Nurahmadie
> yes, it's possible.
>
> The simplest way is to use if and check either $cookie_XXX or
> $http_user_agent variable.
> You may want to explore nginx's wiki page here
> http://w
And what if we are using gzip_static?
As far as I understand, we have to block gzipping page code. But what about
.js .css with no secure content?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,241591,241794#msg-241794
___
nginx mailing list
yes, it's possible.
The simplest way is to use if and check either $cookie_XXX or
$http_user_agent variable.
You may want to explore nginx's wiki page here
http://wiki.nginx.org/HttpCoreModule#.24cookie_COOKIE
On Mon, Aug 12, 2013 at 9:11 PM, Rodrigo Serra Inacio wrote:
> Hi, it's possible to r
Hi, it's possible to rewrite a mobile URL using cookies?
For example, when you acess a URL with a mobile device (android) , nginx
shoul read the cookie and redirect this device according to the android
model ...
Something like this
>From Samsung Galaxy GTI900 redirect to http://mysite.com/gti900
Lukas yeah thanks I will I guess I aggree with you but I am jst asking
On Mon, Aug 12, 2013 at 3:06 PM, Lukas Tribus wrote:
> Hi Dejan,
>
>
> > If I use character reference in html file to represent a character and
> > web server sends the file on browser request, how the browser will
> > decod
Hi Dejan,
> If I use character reference in html file to represent a character and
> web server sends the file on browser request, how the browser will
> decode the character reference?
> My Nginx web server is configured to not send character encoding in the
> header I have set character encodin
If I use character reference in html file to represent a character and web
server sends the file on browser request, how the browser will decode the
character reference?
My Nginx web server is configured to not send character encoding in the
header I have set character encoding in the meta tag on p
On 12 Aug 2013 09:41, "Rakshith" wrote:
>
> So here is what the export policy looks like:
>
> Policy RuleAccess Client RO
> Vserver Name Index Protocol MatchRule
> --- -- -
> -
> vs0
So here is what the export policy looks like:
Policy RuleAccess Client RO
Vserver Name Index Protocol MatchRule
--- -- -
-
vs0 default 1 any 0.0.0.0/0
It makes no difference what file system the file is on. You just need to
ensure that the files are accessible, so take care with uid/gid used to
mount, as well as file ownership. Standard entries in /etc/exports work
from what I remember.
You will have a performance hit to contend with. I usua
On 12 Aug 2013 08:34, "Rakshith" wrote:
>
> Hi,
>
> Can anybody tell me what are the things needed by nginx to forward the
> request via the NFS mount point?? Changes to the config file as such??
Nothing special is needed in my experience. That's the point of NFS
exposing a "normal" file system t
Hi,
Can anybody tell me what are the things needed by nginx to forward the
request via the NFS mount point?? Changes to the config file as such??
The config file looks like as shown below:
http {
.
.
server {
listen *:80 default accept_filter=httpready;
server_nam
15 matches
Mail list logo