Opened 15 years ago
Last modified 14 months ago
#9124 new defect
Request-URI Too Large
Reported by: | darkskuld | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | next-stable-1.6.x |
Component: | general | Version: | |
Severity: | normal | Keywords: | apache url length trac error |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
When i clicked 'create' on the database is locked error I get this apache error.
The requested URL's length exceeds the capacity limit for this server.
Apache/2.0.55 (Ubuntu) DAV/2 SVN/1.3.1 mod_python/3.1.4 Python/2.4.3 mod_ssl/2.0.55 OpenSSL/0.9.8a Server
I have apache configured not to accept URLs longer than 8190 bytes
I would be nice if there was a way to set an optional length limit on tickets created this way. That way, if the description exceeds that limit (say 8kb) it can trim part of the description so that it's still at least possible to create the ticket.
Attachments (1)
Change History (8)
by , 15 years ago
Attachment: | traceback.txt added |
---|
follow-up: 2 comment:1 by , 15 years ago
Milestone: | → next-minor-0.12.x |
---|
follow-up: 3 comment:2 by , 15 years ago
Replying to cboos:
Or we should use POST.
That may be tricky for a remote Trac instance, due to the __FORM_TOKEN
. And in this specific case, creating the ticket on the local Trac instance was probably not a good idea either, as the database was locked :)
comment:3 by , 15 years ago
Replying to rblank:
Replying to cboos:
Or we should use POST.
That may be tricky for a remote Trac instance, due to the
__FORM_TOKEN
. And in this specific case, creating the ticket on the local Trac instance was probably not a good idea either, as the database was locked :)
haha I was able to create a ticket on the local Trac instance after the database unlocked itself. Well at least using the new ticket link.
comment:4 by , 10 years ago
Milestone: | next-minor-0.12.x → next-stable-1.0.x |
---|
comment:5 by , 8 years ago
Milestone: | next-stable-1.0.x → next-stable-1.2.x |
---|
Moved ticket assigned to next-stable-1.0.x since maintenance of 1.0.x is coming to a close. Please move the ticket back if it's critical to fix on 1.0.x.
comment:6 by , 5 years ago
Milestone: | next-stable-1.2.x → next-stable-1.4.x |
---|
Or we should use POST.