You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Yunkai Zhang (JIRA)" <ji...@apache.org> on 2014/04/26 18:10:16 UTC
[jira] [Commented] (TS-2743) Crash with SPDY on production
environment in SpdyNV::SpdyNV
[ https://issues.apache.org/jira/browse/TS-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13982032#comment-13982032 ]
Yunkai Zhang commented on TS-2743:
----------------------------------
[~sudheerv]:
I have tested SPDY with 'Expires' and 'Content-Type' headers, all is ok(to see the SYN_REPLY frame showed as flow):
{code}
[root@test79 ~]# spdycat -3 -v --no-tls http://localhost/a.txt
[ 0.000] Handshake complete
...
[ 0.002] recv SYN_REPLY frame <version=3, flags=0, length=153>
(stream_id=1)
:status: 200 OK
:version: HTTP/1.1
accept-ranges: bytes
age: 1974
cache-control: max-age=86400
content-length: 14
content-type: text/plain
date: Sat, 26 Apr 2014 15:20:26 GMT
etag: "52bfa00f-e"
expires: Sun, 27 Apr 2014 15:20:26 GMT
last-modified: Sun, 29 Dec 2013 04:07:43 GMT
server: ATS/5.0.0
Hello, World!
...
{code}
According rfc2616/rfc1123/rfc822:
{code}
The format is an absolute date and time as defined by HTTP-date in section 3.3.1; it MUST be in RFC 1123 date format:
Expires = "Expires" ":" HTTP-date
An example of its use is
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Note: if a response includes a Cache-Control field with the max-
age directive (see section 14.9.3), that directive overrides the
Expires field.
{code}
IIUC, the value of 'Expires' header, as well as 'Content-Type', must be string and can't be NULL.
It seems that your original server returns invalid value of 'Expires' and 'Content-Type' ?
> Crash with SPDY on production environment in SpdyNV::SpdyNV
> -----------------------------------------------------------
>
> Key: TS-2743
> URL: https://issues.apache.org/jira/browse/TS-2743
> Project: Traffic Server
> Issue Type: Bug
> Components: Core, SPDY
> Reporter: Sudheer Vinukonda
> Assignee: Yunkai Zhang
> Labels: SPDY_ATS
>
> After patching a fix (by removing the apparent incorrect assert failure on non-ipv4 address in TsFetchCreate - jira ts-2742), noticed a new crash, this time in SpdyNV::SpdyNV with the below stack trace. Will update more upon investigation.
> FATAL: SpdyCommon.cc:133: failed assert `value && value_len`
> FATAL: SpdyCommon.cc:133: failed assert `value && value_len`
> /home/y/bin/traffic_server - STACK TRACE:
> /home/y/bin/traffic_server - STACK TRACE:
> /home/y/lib64/libtsutil.so.5(+0x1f5c8)[0x2b7371f6a5c8]
> /home/y/lib64/libtsutil.so.5(+0x1f5c8)[0x2b7371f6a5c8]
> /home/y/lib64/libtsutil.so.5(+0x1da8f)[0x2b7371f68a8f]
> /home/y/lib64/libtsutil.so.5(+0x1da8f)[0x2b7371f68a8f]
> /home/y/bin/traffic_server[0x4af739]
> /home/y/bin/traffic_server[0x5cf7ea]
> /home/y/bin/traffic_server[0x5d0a6a]
> /home/y/bin/traffic_server(_ZN7FetchSM15InvokePluginExtEi+0x33a)[0x4c7a5a]
> /home/y/bin/traffic_server[0x4af739]
> /home/y/bin/traffic_server(_ZN7FetchSM18process_fetch_readEi+0x187)[0x4c7f37]
> /home/y/bin/traffic_server[0x5cf7ea]
> /home/y/bin/traffic_server[0x5d0a6a]
> /home/y/bin/traffic_server(_ZN7FetchSM15InvokePluginExtEi+0x33a)[0x4c7a5a]
> /home/y/bin/traffic_server(_ZN7FetchSM18process_fetch_readEi+0x187)[0x4c7f37]
> /home/y/bin/traffic_server(_ZN7FetchSM13fetch_handlerEiPv+0x8b)[0x4c80eb]
> /home/y/bin/traffic_server(_ZN8PluginVC17process_read_sideEb+0x375)[0x4dd0d5]
> /home/y/bin/traffic_server(_ZN8PluginVC18process_write_sideEb+0x57a)[0x4dda2a]
> /home/y/bin/traffic_server(_ZN7FetchSM13fetch_handlerEiPv+0x8b)[0x4c80eb]
> /home/y/bin/traffic_server(_ZN8PluginVC12main_handlerEiPv+0x372)[0x4de272]
> /home/y/bin/traffic_server(_ZN8PluginVC17process_read_sideEb+0x375)[0x4dd0d5]
> /home/y/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x8f)[0x712f7f]
> /home/y/bin/traffic_server(_ZN8PluginVC18process_write_sideEb+0x57a)[0x4dda2a]
> /home/y/bin/traffic_server(_ZN7EThread7executeEv+0x61b)[0x713aab]
> /home/y/bin/traffic_server(_ZN8PluginVC12main_handlerEiPv+0x372)[0x4de272]
> /home/y/bin/traffic_server[0x71232a]
> /home/y/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x8f)[0x712f7f]
> /lib64/libpthread.so.0(+0x3297207851)[0x2b7372601851]
> /home/y/bin/traffic_server(_ZN7EThread7executeEv+0x61b)[0x713aab]
> /lib64/libc.so.6(clone+0x6d)[0x3296ee890d]
> /home/y/bin/traffic_server[0x71232a]
> /lib64/libpthread.so.0(+0x3297207851)[0x2b7372601851]
--
This message was sent by Atlassian JIRA
(v6.2#6252)