Hi,
On Sat, Jun 25, 2016, at 14:42, Lebod wrote:
> Thank you for the reply Francis,
>
> I have only 1 server {} with "example.com".
>
> I have one server block that listens on ports 80 and 443 to example.com
> and
> redirects to https://www.example.com like this:
>
> server {
> listen 80;
>
Thank you for the reply Francis,
I have only 1 server {} with "example.com".
I have one server block that listens on ports 80 and 443 to example.com and
redirects to https://www.example.com like this:
server {
listen 80;
listen 443 ssl;
server_name example.com ***IP Address***;
return 301 h
Hello,
I attached a trivial patch that fixes the build. OpenSSL removed unused error
codes and SSL_R_NO_CIPHERS_PASSED was one of them.
Apply with:
patch -p1 < 0001-Fix-nginx-build.patch
Kurt Cancemi
https://www.x64architecture.com
0001-Fix-nginx-build.patch
Description: Binary data
> On J
No reason? The API/ABI wasn't stable either with the release of the
previous patches to made it compatible with OpenSSl's pre-release for
example @Gobelet's patch.
If someone made a patch, please let me know.
> On Sat, Jun 25, 2016 at 01:58:27AM +0200, rik...@deds.nl wrote:
>>
>> There could be
On Sat, Jun 25, 2016 at 01:58:27AM +0200, rik...@deds.nl wrote:
>
> There could be someone who has a pre-patch for version 6, who is also
> testing OpenSSL, just like @Gobelet's patch did before with pre 5.
No reason for this until API/ABI will be stable.
--
Sergey A. Osokin
___
On Fri, Jun 24, 2016 at 03:10:08AM -0400, charles13 wrote:
Hi there,
> I wonder is there any way to limit_rate based on file extension in Nginx,
> for example, putting different rate limit rules on flv and mp4?
I've not tested it, but it should Just Work.
limit_rate can work in location{}, so p
On Fri, Jun 24, 2016 at 12:45:00AM -0400, Lebod wrote:
Hi there,
> Thanks for the tip Francis but Nginx -T doesn't give me a clue at all.
> Would you know what specifically I can change to fix this?
You have two server{} blocks that have server_name example.com.
That is a problem.
Decide what
Hi,
That was not the question.
There could be someone who has a pre-patch for version 6, who is also
testing OpenSSL, just like @Gobelet's patch did before with pre 5.
> Hi,
>
> it already has been discussed,
> https://trac.nginx.org/nginx/ticket/860#comment:10
>
> On Fri, Jun 24, 2016 at 10:05:0
Hi,
it already has been discussed,
https://trac.nginx.org/nginx/ticket/860#comment:10
On Fri, Jun 24, 2016 at 10:05:00PM +0200, rik...@deds.nl wrote:
> Hi,
>
> Does someone have a OpenSSL 1.1.0 Pre 6 patch for Nginx 1.11.*?
>
> So that it is possible to compile Nginx 1.11.* with the latest Ope
Hi nanaya,
today I run a few tests.
this URL:
http://www.website.com/index.php?lvl=cmspage&pageid=14&id_article=52
Return only: http://www.website.com/index.php?lvl=cmspage
you would know how to fix?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,267813,267866#msg-267866
__
Hi,
Does someone have a OpenSSL 1.1.0 Pre 6 patch for Nginx 1.11.*?
So that it is possible to compile Nginx 1.11.* with the latest OpenSSL
1.1.0 Pre 6 git clone (today).
Want to test some new OpenSSL 1.1.0 features, with the latest Git clone as
OpenSSL version 1.1 seems near final.
"src/event/n
​Thanks for your reply. It sounds great!
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
anybody don't know about that ?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,267827,267861#msg-267861
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On 06/24/2016 10:34 AM, A. Schulze wrote:
shouldn't that say "httpS:// ..." ?
Yes,
thanks,
JG
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On 06/24/2016 10:29 AM, John Griessen wrote:
The problem is with the moderation page. When submitting a change,
a security warning pops up saying info will not be encrypted
I found what this needed from Mark Sapiro:
put
DEFAULT_URL_PATTERN = 'https://%s/mailman/'
in mm,_cfg.py ad then rerun
John Griessen:
I checked and my configuration had:
DEFAULT_URL_PATTERN = 'http://%s/mailman/'
shouldn't that say "httpS:// ..." ?
Andreas
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
mailman version 2.1.22 works fine for my webpages I set up such as
http://cibolo.us/mailman/listinfo/open_electroporator that URl is rewritten
and permenanently directed to below:
https://cibolo.us/mailman/listinfo/open_electroporator
The problem is with the moderation page. When submitting a
Why do you have that in a separate server block?
On Fri, Jun 24, 2016 at 9:31 AM, Zeal Vora wrote:
> Thanks. The above lined helped. However one more doubt. I want NGINX to
> return 200 whenever some one goes to /nature , so I wrote above
> configuration, however when some one goes to /nature ,
On 23 Jun 2016, at 13:58, Jorge L. wrote:
> I've continued with my attempt to integrate my routing logic as javascript
> code.
>
> Regarding my previous feedback, it is possible to iterate the keys of an
> object with "for ... in". However, you cannot use "var" keyword to assign the
> result
Thanks. The above lined helped. However one more doubt. I want NGINX to
return 200 whenever some one goes to /nature , so I wrote above
configuration, however when some one goes to /nature , NGINX gives it 404
instead of 200. Here is my configuration :-
server {
location = /nature {
return 200
Hello,
I wonder is there any way to limit_rate based on file extension in Nginx,
for example, putting different rate limit rules on flv and mp4?
I've tried this, but somehow returned file not found
location ~* \.(flv|f4v)$ {
limit_rate_after 1m;
limit_rate 80k;
}
location ~* \.(mp4|m4v)$ {
limi
21 matches
Mail list logo
