Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
O
opentrafficshaper
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Yuriy
opentrafficshaper
Commits
180f6c31
Commit
180f6c31
authored
11 years ago
by
Nigel Kukard
Browse files
Options
Downloads
Patches
Plain Diff
Fixed HTTP bug where content was not passed
parent
c9947523
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
opentrafficshaper/POE/Filter/HybridHTTP.pm
+4
-4
4 additions, 4 deletions
opentrafficshaper/POE/Filter/HybridHTTP.pm
with
4 additions
and
4 deletions
opentrafficshaper/POE/Filter/HybridHTTP.pm
+
4
−
4
View file @
180f6c31
...
@@ -95,7 +95,7 @@ sub get_one
...
@@ -95,7 +95,7 @@ sub get_one
# Waiting for content.
# Waiting for content.
}
elsif
(
$self
->
{'
state
'}
==
ST_HTTP_CONTENT
)
{
}
elsif
(
$self
->
{'
state
'}
==
ST_HTTP_CONTENT
)
{
return
$self
->
_get_one_http_
headers
();
return
$self
->
_get_one_http_
content
();
# Websocket
# Websocket
}
elsif
(
$self
->
{'
state
'}
==
ST_WEBSOCKET_STREAM
)
{
}
elsif
(
$self
->
{'
state
'}
==
ST_WEBSOCKET_STREAM
)
{
...
@@ -282,12 +282,12 @@ sub _get_one_http_headers
...
@@ -282,12 +282,12 @@ sub _get_one_http_headers
# does not include defined semantics for an entity-body, then the
# does not include defined semantics for an entity-body, then the
# message-body SHOULD be ignored when handling the request.
# message-body SHOULD be ignored when handling the request.
# - RFC2616
# - RFC2616
if
(
!
defined
(
$content_length
)
||
!
defined
(
$content_encoding
))
{
if
(
!
defined
(
$content_length
)
&&
!
defined
(
$content_encoding
))
{
$self
->
{'
request
'}
=
$request
;
$self
->
{'
request
'}
=
$request
;
$self
->
_reset
();
$self
->
_reset
();
return
[
$request
];
return
[
$request
];
}
}
# PG- GET shouldn't have a body. But RFC2616 talks about Content-Length
# PG- GET shouldn't have a body. But RFC2616 talks about Content-Length
# for HEAD. And My reading of RFC2616 is that HEAD is the same as GET.
# for HEAD. And My reading of RFC2616 is that HEAD is the same as GET.
# So logically, GET can have a body. And RFC2616 says we SHOULD ignore
# So logically, GET can have a body. And RFC2616 says we SHOULD ignore
...
@@ -330,7 +330,7 @@ sub _get_one_http_headers
...
@@ -330,7 +330,7 @@ sub _get_one_http_headers
$self
->
{'
state
'}
=
ST_HTTP_CONTENT
;
$self
->
{'
state
'}
=
ST_HTTP_CONTENT
;
$self
->
{'
request
'}
=
$request
;
$self
->
{'
request
'}
=
$request
;
return
[
]
;
$self
->
_get_one_http_content
()
;
}
}
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment