I've started playing around with boringssl with nginx.
Mostly everything works except OCSP. Seems like either openssl 1.0.2
which boringssl was forked from does not have it, or the boringssl
folk ripped it out. I have not investigated.
Anyway, I'm please to report everything seems to work!
--
#
Am 13.07.2014 22:01 schrieb "Valentin V. Bartenev" :
>
> Have you tried nginx SSI module?
> http://nginx.org/en/docs/http/ngx_http_ssi_module.html
We're using the SSI module to assemble the page from various backends, but
how could SSIs help to send the head or page header early to the client?
Ch
Hello!
On Sun, Jul 13, 2014 at 05:46:50PM -0400, itpp2012 wrote:
> Ok clear enough, I'd still consider it some kind of bug (it makes no sense
> for try_files to be disabled when an if matches), for example using map and
> a single IF does this as well which is more or less nginx's recommended way
Ok clear enough, I'd still consider it some kind of bug (it makes no sense
for try_files to be disabled when an if matches), for example using map and
a single IF does this as well which is more or less nginx's recommended way
of doing an IF with map.
Funny thing is when you have a .php location i
Hello!
On Sun, Jul 13, 2014 at 09:22:39AM -0400, mex wrote:
> https://www.mare-system.de/blog/page/1405201517/
Just a quick comment: OpenSSL's libs under ".openssl/" isn't a
result of OpenSSL's behaviour, but rather a result of "make
install" nginx calls (and the ".openssl" install prefix it
Hello!
On Sat, Jul 12, 2014 at 06:23:41AM -0400, itpp2012 wrote:
> Hmm, more debugging, this config returns a 404 from the backend (which it
> shouldn't):
>
> try_files $uri $uri/ =404;
> set $maintmode S;
> if ($remote_addr ~ "^(192.168.*.*)$") { set $maintmode L; }
> if (-f $document_root/mai
Denis S. Filimonov wrote in post #645832:
> I had the same problem some time ago.
> The problem with this script is that it violates CGI specifications
> regarding
> POST requests. POSTed data must come to a CGI app from the standard
> input
> while this script parses the input and sets variables a
On Sunday 13 July 2014 14:49:18 Martin Grotzke wrote:
> Hi all,
>
> inspired by the bigpipe pattern I'm wondering if it's possible to send the
> full html head so that the browser can start downloading CSS and javascript
> files.
>
> An idea would be that the proxied backend uses a chunked encodi
Am 13.07.2014 18:37 schrieb "mex" :
>
> in your case i'd say the cleanest way would be a reengineering
> of your application; the other way would imply a full regex
> on every request coming back from your app-servers to filter out
> those stuff that already has been send.
> the problem: appservers
> Ok, I haven't done anything with nginx+lua so far, need to check out
> what
> can be done with lua. Can you give some direction how lua can be
> helpful here?
oh ... lua might be used to manipulate every single phase of a request
coming to and processed by nginx; so a swiss army knife
super-ext
Am 13.07.2014 15:40 schrieb "mex" :
>
> sounds more like a custom solution that might be achieved using lua +
nginx;
Ok, I haven't done anything with nginx+lua so far, need to check out what
can be done with lua. Can you give some direction how lua can be helpful
here?
> from what i understand yo
15:54 13-7-2014 nginx 1.7.4.1 RedKnight
Based on nginx 1.7.4 (11-7-2014, last changeset 5767:abd460ece11e) with;
+ lua-nginx-module v0.9.11 (upgraded 12-7-2014)
+ echo-nginx-module v0.54 (upgraded 3-7-2014)
+ form-input-nginx-module v0.09 (upgraded 3-7-2014)
+ Source changes back ported
+ Source c
sounds more like a custom solution that might be achieved using lua + nginx;
from what i understand you have a "static" part that should get send
early/from
cache and a "dynamic" part that must wait for the backend?
the only solution i could think of in such an asynchronous delivery
is using ng
https://www.mare-system.de/blog/page/1405201517/
# Summary
It works.
While it is not recommended to substitude OpenSSL with LibreSSL in this
early stage, i wanted to test if it is possible. And it is. There are no
functional or performance-issues, as far as i can test, and building nginx +
libre
Hi all,
inspired by the bigpipe pattern I'm wondering if it's possible to send the
full html head so that the browser can start downloading CSS and javascript
files.
An idea would be that the proxied backend uses a chunked encoding and sends
the html head as first chunk. The body would be sent as
15 matches
Mail list logo
