Custom Query (2297 matches)

Hello,

I am trying to add nginx-1.0.5.tar.gz package to Wind River Linux. The host machine I am using is Ubuntu 10.04. Nginx package got compiled and it created install directories and files in /usr/local/nginx folder. But during the final creation of kernel image and RFS we are getting below error.

Installing RPMs into filesystem directory Preparing... ################################################## setup ################################################## error: Failed dependencies: libcrypto.so.0.9.8 is needed by nginx-1.0.5-1_WR4.1.0.0.x86_64 libcrypto.so.0.9.8(OPENSSL_0.9.8) is needed by nginx-1.0.5-1_WR4.1.0.0.x86_64

I got this this error after adding 'openssl-dev' package to our Ubuntu machine through apt-get. Before adding this package Wind River kernel image and RFS is created successfully.

On analysis I found that in nginx-1.0.5\objs\ngx_auto_config.h, following addtional #defines are setting in the not working source code #ifndef NGX_OPENSSL_MD5 #define NGX_OPENSSL_MD5 1 #endif

#ifndef NGX_HAVE_OPENSSL_MD5_H #define NGX_HAVE_OPENSSL_MD5_H 1 #endif

#ifndef NGX_HAVE_MD5 #define NGX_HAVE_MD5 1 #endif

#ifndef NGX_HAVE_SHA1 #define NGX_HAVE_SHA1 1 #endif

#ifndef NGX_HAVE_OPENSSL_SHA1_H #define NGX_HAVE_OPENSSL_SHA1_H 1 #endif

Could you please tell me what could be the issue. Does nginx looks for the openssl/libcrypto library versions of host machine during configuration and compilation.

Regards Sivan

If upstream does not send last-modified header, @ style expiry times will be interpreted as (now + time)

(from r1.0.8)

ngx_http_headers_filter_module.c line 266 the bug is that the expires header is not set correctly when using @ and it is the case that it is not set correctly, but you will only see the bug if upstream does not set a last-modified header

 if (conf->expires == NGX_HTTP_EXPIRES_ACCESS
        || r->headers_out.last_modified_time == -1)
    {

its the || condition that causes the problem

confirmed on #nginx by PiotrSikora

ngx_vslprintf(u_char *buf, u_char *last, const char *fmt, va_list args) when fmt is terminated by '%', there will be invalid write of zero byte to buf and unknown behaviour afterwards.

Correct behaviour is to write terminated '%' to buf (for example, this approach is applied in linux kernel lib/vsprintf.c).