Opened 7 years ago

Closed 7 years ago

#322 closed defect (invalid)

Nginx failed to serve SSL

Reported by: launchpad.net/~vulzscht Owned by:
Priority: minor Milestone:
Component: nginx-core Version: 1.2.x
Keywords: Cc:
uname -a: Linux ip-... 2.6.32-343-ec2 #45-Ubuntu SMP Tue Feb 14 18:18:17 UTC 2012 x86_64 GNU/Linux
nginx -V: nginx version: nginx/1.0.14 built by gcc 4.4.3 (Ubuntu 4.4.3-4ubuntu5.1) TLS SNI support enabled configure arguments: --prefix=/opt/nginx --with-http_stub_status_module --with-http_ssl_module --with-http_realip_module --with-http_addition_module --with-http_sub_module --with-http_flv_module --with-http_gzip_static_module --with-http_random_index_module --with-http_secure_link_module --with-http_degradation_module --without-http_empty_gif_module --without-select_module --without-http_userid_module --without-http_autoindex_module --without-http_map_module --without-mail_pop3_module --without-mail_imap_module --without-mail_smtp_module --user=nginx --group=nginx --add-module=../nginx-upstream-jvm-route-read-only/

Description

when creating SSL server i had mistype in
server_name directive (had no semicolon in the end of line)

i.e.
server_name server
instead of
server_name server;

nginx started, but SSL requests failed for no obvious reason with the following error

2013/03/21 02:56:58 [info] 27558#0: *3919219 client sent invalid method while reading client request line, client: YYY, server: XXX, request: "VC@@UA@@QC@QJ<BD>Jyo<D8><EF><D7>J<CB><F1>+<8E><B7><8D><F9>D<8D><A9>n<F6>%<9C>3?q<B3><9C><C5>L<A4>@@*@<FF>@<88>@<87>@9@8@<84>@5@E@D@f@3@2@<96>@A@D@E@/@V@S<FE><FF>@"

i suppose nginx should return syntax error

reproduced on version 1.0.14 and 1.2.7

Change History (1)

comment:1 Changed 7 years ago by mdounin

  • Resolution set to invalid
  • Status changed from new to closed

Missing semicolon means you have config which is different from one with a semicolon. If it happens to be syntactically valid - there is no surprise it works, but does something different from what you expect.

Note: See TracTickets for help on using tickets.