Seems like maybe something is broken on the nginx packages download.
For example, if I curl this endpoint I get a set of results from 31-Jul-2018
$ curl https://nginx.org/packages/rhel/7/x86_64/repodata/
Index of /packages/rhel/7/x86_64/repodata/
Index of /packages/rhel/7/x86_64/repodata/../
43
Thanks Valentin! I didn't realize fancyindex could be the culprit. I'll
follow up with the fancyindex developer.
On Thu, Oct 16, 2014 at 5:58 AM, Valentin V. Bartenev
wrote:
> On Wednesday 15 October 2014 19:24:11 Greg Barker wrote:
> > Thanks Valentin. Here
.conf --sbin-path=/opt/nginx-1.6.2/sbin/nginx
--with-http_ssl_module --with-http_gzip_static_module
--with-http_spdy_module --add-module=/tmp/nginx_http_fancyindex_module
On Wed, Oct 15, 2014 at 5:35 PM, Valentin V. Bartenev
wrote:
> On Monday 06 October 2014 12:25:37 Greg Barker wrote:
> > I
Bump. Any ideas on this one? Some other folks on HN were experiencing this
as well: https://news.ycombinator.com/item?id=8404790
On Mon, Oct 6, 2014 at 12:25 PM, Greg Barker wrote:
> I'm using nginx 1.6.2 w/ SPDY to serve an autoindex of static files. After
> I start downloading a
i-socket>
parameter? I'm not sure.
I don't know of a good guide to follow, I had to piece mine together from a
bunch of different guides of varying quality until I got it working.
Greg
On Thu, Oct 9, 2014 at 1:52 PM, Steven Williams <
theblessedadventh...@gmail.com> wrote:
&g
Option #2 should work, here's what I have for my uwsgi site. Double check
your permissions on the directory the uwsgi.sock lives in.
My nginx conf:
location / {
uwsgi_pass unix:///var/www/my_app/my_virtualenv/run/uwsgi.sock;
include uwsgi_params;
}
Directory permissions:
$ ls -la /var/ww
I'm using nginx 1.6.2 w/ SPDY to serve an autoindex of static files. After
I start downloading a file, I can no longer access other pages on the site.
I get a Firefox error message "The connection was interrupted" - a similar
message appears in Chrome. If I do a CTRL+F5, then I can browse the site
ack exchange that sounded very similar to our issue
that involved turning off sendfile, however this did not appear to affect the
behavior at all. We do not have any caching turned on.
Does anyone have any idea what could be going on here?
Thanks!
G
but I can't do that as "location / {}" is in a common config
included by many other vhosts.
--
Greg
Document sans nom
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Le 06/08/2013 16:22, Jonathan Matthews a écrit :
> Just checking you're aware that this only matches "/allowed/" by
> itself and nothing below it.
>
> Is that what you meant? Is that what you're testing?
>
>
It match evrything that _starts_ with /allowed/
allow all;
}
deny all;
}
I short, I want to disallow access on my website, only some IPs can
access, except for /allowed/ which is open.
What's wrong ?
Greg
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hi Maxim,
Is ipv6 upstream support available in nginx's proxy modules just yet?
Thanks,
Greg
smime.p7s
Description: S/MIME cryptographic signature
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
he store. We would also want this for
in-progress caching attempts, for example if I requested cdn.blah.com/1.mp4 on
a 2nd machine, before the first machine's request for the same file has had a
chance to fully cache in the store.
Thanks in advance for any assistance!
Regards,
Greg
__
13 matches
Mail list logo