Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
N
nghttp2
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Libraries
nghttp2
Commits
0f4d01c2
Commit
0f4d01c2
authored
Jul 03, 2014
by
Tatsuhiro Tsujikawa
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
nghttpx: Pass through NGHTTP2_NO_ERROR from downstream to upstream
parent
f8b87209
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
5 deletions
+7
-5
src/shrpx_http2_upstream.cc
src/shrpx_http2_upstream.cc
+7
-5
No files found.
src/shrpx_http2_upstream.cc
View file @
0f4d01c2
...
@@ -539,12 +539,14 @@ namespace {
...
@@ -539,12 +539,14 @@ namespace {
nghttp2_error_code
infer_upstream_rst_stream_error_code
nghttp2_error_code
infer_upstream_rst_stream_error_code
(
nghttp2_error_code
downstream_error_code
)
(
nghttp2_error_code
downstream_error_code
)
{
{
//
Only propagate NGHTTP2_REFUSED_STREAM so that upstream client
//
NGHTTP2_REFUSED_STREAM is important because it tells upstream
// c
an resend request
.
// c
lient to retry
.
if
(
downstream_error_code
!=
NGHTTP2_REFUSED_STREAM
)
{
switch
(
downstream_error_code
)
{
return
NGHTTP2_INTERNAL_ERROR
;
case
NGHTTP2_NO_ERROR
:
}
else
{
case
NGHTTP2_REFUSED_STREAM
:
return
downstream_error_code
;
return
downstream_error_code
;
default:
return
NGHTTP2_INTERNAL_ERROR
;
}
}
}
}
}
// namespace
}
// namespace
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment