[jira] [Updated] (TS-3946) Invalid pad length in HTTP/2

2016-09-08 Thread Masaori Koshiba (JIRA) 

 [ 
https://issues.apache.org/jira/browse/TS-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Masaori Koshiba updated TS-3946:

Fix Version/s: (was: 7.1.0)
   7.0.0

> Invalid pad length in HTTP/2
> 
>
> Key: TS-3946
> URL: https://issues.apache.org/jira/browse/TS-3946
> Project: Traffic Server
>  Issue Type: Bug
>  Components: HTTP/2
>Reporter: Leif Hedstrom
>Assignee: Masaori Koshiba
> Fix For: 7.0.0
>
>
> This is an h2spec issue:
> {code}
>   6.1. DATA
> ✓ Sends a DATA frame with 0x0 stream identifier
> ✓ Sends a DATA frame on the stream that is not opend
> × Sends a DATA frame with invalid pad length
>   - The endpoint MUST treat this as a connection error of type 
> PROTOCOL_ERROR.
> Expected: GOAWAY frame (ErrorCode: PROTOCOL_ERROR)
>   RST_STREAM frame (ErrorCode: PROTOCOL_ERROR)
>   Connection close
>   Actual: RST_STREAM frame (Length: 4, Flags: 0, ErrorCode: 
> STREAM_CLOSED)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (TS-3946) Invalid pad length in HTTP/2

2016-09-08 Thread Leif Hedstrom (JIRA) 

 [ 
https://issues.apache.org/jira/browse/TS-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leif Hedstrom updated TS-3946:
--
Fix Version/s: (was: 7.0.0)
   7.1.0

> Invalid pad length in HTTP/2
> 
>
> Key: TS-3946
> URL: https://issues.apache.org/jira/browse/TS-3946
> Project: Traffic Server
>  Issue Type: Bug
>  Components: HTTP/2
>Reporter: Leif Hedstrom
>Assignee: Masaori Koshiba
> Fix For: 7.1.0
>
>
> This is an h2spec issue:
> {code}
>   6.1. DATA
> ✓ Sends a DATA frame with 0x0 stream identifier
> ✓ Sends a DATA frame on the stream that is not opend
> × Sends a DATA frame with invalid pad length
>   - The endpoint MUST treat this as a connection error of type 
> PROTOCOL_ERROR.
> Expected: GOAWAY frame (ErrorCode: PROTOCOL_ERROR)
>   RST_STREAM frame (ErrorCode: PROTOCOL_ERROR)
>   Connection close
>   Actual: RST_STREAM frame (Length: 4, Flags: 0, ErrorCode: 
> STREAM_CLOSED)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (TS-3946) Invalid pad length in HTTP/2

2016-08-17 Thread Alan M. Carroll (JIRA) 

 [ 
https://issues.apache.org/jira/browse/TS-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan M. Carroll updated TS-3946:

Assignee: Masaori Koshiba

> Invalid pad length in HTTP/2
> 
>
> Key: TS-3946
> URL: https://issues.apache.org/jira/browse/TS-3946
> Project: Traffic Server
>  Issue Type: Bug
>  Components: HTTP/2
>Reporter: Leif Hedstrom
>Assignee: Masaori Koshiba
> Fix For: 7.0.0
>
>
> This is an h2spec issue:
> {code}
>   6.1. DATA
> ✓ Sends a DATA frame with 0x0 stream identifier
> ✓ Sends a DATA frame on the stream that is not opend
> × Sends a DATA frame with invalid pad length
>   - The endpoint MUST treat this as a connection error of type 
> PROTOCOL_ERROR.
> Expected: GOAWAY frame (ErrorCode: PROTOCOL_ERROR)
>   RST_STREAM frame (ErrorCode: PROTOCOL_ERROR)
>   Connection close
>   Actual: RST_STREAM frame (Length: 4, Flags: 0, ErrorCode: 
> STREAM_CLOSED)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (TS-3946) Invalid pad length in HTTP/2

2016-04-06 Thread Leif Hedstrom (JIRA) 

 [ 
https://issues.apache.org/jira/browse/TS-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leif Hedstrom updated TS-3946:
--
Fix Version/s: (was: 6.2.0)
   7.0.0

> Invalid pad length in HTTP/2
> 
>
> Key: TS-3946
> URL: https://issues.apache.org/jira/browse/TS-3946
> Project: Traffic Server
>  Issue Type: Bug
>  Components: HTTP/2
>Reporter: Leif Hedstrom
> Fix For: 7.0.0
>
>
> This is an h2spec issue:
> {code}
>   6.1. DATA
> ✓ Sends a DATA frame with 0x0 stream identifier
> ✓ Sends a DATA frame on the stream that is not opend
> × Sends a DATA frame with invalid pad length
>   - The endpoint MUST treat this as a connection error of type 
> PROTOCOL_ERROR.
> Expected: GOAWAY frame (ErrorCode: PROTOCOL_ERROR)
>   RST_STREAM frame (ErrorCode: PROTOCOL_ERROR)
>   Connection close
>   Actual: RST_STREAM frame (Length: 4, Flags: 0, ErrorCode: 
> STREAM_CLOSED)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (TS-3946) Invalid pad length in HTTP/2

2015-12-16 Thread Leif Hedstrom (JIRA) 

 [ 
https://issues.apache.org/jira/browse/TS-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leif Hedstrom updated TS-3946:
--
Fix Version/s: (was: 6.1.0)
   6.2.0

> Invalid pad length in HTTP/2
> 
>
> Key: TS-3946
> URL: https://issues.apache.org/jira/browse/TS-3946
> Project: Traffic Server
>  Issue Type: Bug
>  Components: HTTP/2
>Reporter: Leif Hedstrom
> Fix For: 6.2.0
>
>
> This is an h2spec issue:
> {code}
>   6.1. DATA
> ✓ Sends a DATA frame with 0x0 stream identifier
> ✓ Sends a DATA frame on the stream that is not opend
> × Sends a DATA frame with invalid pad length
>   - The endpoint MUST treat this as a connection error of type 
> PROTOCOL_ERROR.
> Expected: GOAWAY frame (ErrorCode: PROTOCOL_ERROR)
>   RST_STREAM frame (ErrorCode: PROTOCOL_ERROR)
>   Connection close
>   Actual: RST_STREAM frame (Length: 4, Flags: 0, ErrorCode: 
> STREAM_CLOSED)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (TS-3946) Invalid pad length in HTTP/2

2015-11-05 Thread Leif Hedstrom (JIRA) 

 [ 
https://issues.apache.org/jira/browse/TS-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leif Hedstrom updated TS-3946:
--
Assignee: (was: Leif Hedstrom)

> Invalid pad length in HTTP/2
> 
>
> Key: TS-3946
> URL: https://issues.apache.org/jira/browse/TS-3946
> Project: Traffic Server
>  Issue Type: Bug
>  Components: HTTP/2
>Reporter: Leif Hedstrom
> Fix For: 6.1.0
>
>
> This is an h2spec issue:
> {code}
>   6.1. DATA
> ✓ Sends a DATA frame with 0x0 stream identifier
> ✓ Sends a DATA frame on the stream that is not opend
> × Sends a DATA frame with invalid pad length
>   - The endpoint MUST treat this as a connection error of type 
> PROTOCOL_ERROR.
> Expected: GOAWAY frame (ErrorCode: PROTOCOL_ERROR)
>   RST_STREAM frame (ErrorCode: PROTOCOL_ERROR)
>   Connection close
>   Actual: RST_STREAM frame (Length: 4, Flags: 0, ErrorCode: 
> STREAM_CLOSED)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (TS-3946) Invalid pad length in HTTP/2

2015-09-25 Thread Leif Hedstrom (JIRA) 

 [ 
https://issues.apache.org/jira/browse/TS-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leif Hedstrom updated TS-3946:
--
Fix Version/s: 6.1.0

> Invalid pad length in HTTP/2
> 
>
> Key: TS-3946
> URL: https://issues.apache.org/jira/browse/TS-3946
> Project: Traffic Server
>  Issue Type: Bug
>  Components: HTTP/2
>Reporter: Leif Hedstrom
> Fix For: 6.1.0
>
>
> This is an h2spec issue:
> {code}
>   6.1. DATA
> ✓ Sends a DATA frame with 0x0 stream identifier
> ✓ Sends a DATA frame on the stream that is not opend
> × Sends a DATA frame with invalid pad length
>   - The endpoint MUST treat this as a connection error of type 
> PROTOCOL_ERROR.
> Expected: GOAWAY frame (ErrorCode: PROTOCOL_ERROR)
>   RST_STREAM frame (ErrorCode: PROTOCOL_ERROR)
>   Connection close
>   Actual: RST_STREAM frame (Length: 4, Flags: 0, ErrorCode: 
> STREAM_CLOSED)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)