Ticket #9124 (new defect)
Opened 2 years ago
Last modified 2 years ago
Request-URI Too Large
| Reported by: | darkskuld | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | next-minor-0.12.x |
| Component: | general | Version: | |
| Severity: | normal | Keywords: | apache url length trac error |
| Cc: | |||
| Release Notes: | |||
| API 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
Change History
Changed 2 years ago by darkskuld
- Attachment traceback.txt added
comment:1 follow-up: ↓ 2 Changed 2 years ago by cboos
- Milestone set to next-minor-0.12.x
comment:2 in reply to: ↑ 1 ; follow-up: ↓ 3 Changed 2 years ago by 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 :)
comment:3 in reply to: ↑ 2 Changed 2 years ago by darkskuld
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.
Or we should use POST.