Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Z
Zope
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
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
Zope
Commits
3194ed1e
Commit
3194ed1e
authored
Apr 29, 2004
by
Paul Winkler
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
parent
20b99970
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
0 deletions
+7
-0
lib/python/ZServer/HTTPServer.py
lib/python/ZServer/HTTPServer.py
+7
-0
No files found.
lib/python/ZServer/HTTPServer.py
View file @
3194ed1e
...
@@ -365,6 +365,13 @@ class zhttp_channel(http_channel):
...
@@ -365,6 +365,13 @@ class zhttp_channel(http_channel):
# we are receiving header (request) data
# we are receiving header (request) data
self
.
in_buffer
=
self
.
in_buffer
+
data
self
.
in_buffer
=
self
.
in_buffer
+
data
if
len
(
self
.
in_buffer
)
>
self
.
max_header_len
:
if
len
(
self
.
in_buffer
)
>
self
.
max_header_len
:
# Don't bother with a proper response header,
# we are probably under attack and that would just consume
# precious resources.
# Instead, just bail out and leave the nasty client hanging.
# Hanging's too good for them!
# Unfortunate side effect: the attack gets logged to the
# event log, but not the access log.
raise
ValueError
(
'HTTP headers invalid (too long)'
)
raise
ValueError
(
'HTTP headers invalid (too long)'
)
class
zhttp_server
(
http_server
):
class
zhttp_server
(
http_server
):
...
...
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