Summary: | https://bugs.gentoo.org: POST /post_bug.cgi: 500 Internal server error | ||
---|---|---|---|
Product: | Gentoo Infrastructure | Reporter: | Alexander Bezrukov <phmagic> |
Component: | Bugzilla | Assignee: | Bugzilla Admins <bugzilla> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | mgorny |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Alexander Bezrukov
2022-06-16 21:43:22 UTC
It seems that I see the problem: a too large attachment. Anyway, a more informative error message would be helpful. How large was the attachment, exactly? I've just tried with a 4 MiB file, and Bugzilla correctly responded with a big red warning. If it happens while creating a bug, it creates a bug without the attachment instead but I've never seen it 500 over that. I've also tried a 300 MiB file now. Took a while but eventually big red error showed. (In reply to Michał Górny from comment #2) > How large was the attachment, exactly? I've just tried with a 4 MiB file, > and Bugzilla correctly responded with a big red warning. If it happens > while creating a bug, it creates a bug without the attachment instead but > I've never seen it 500 over that. It was 14MB. Actually, it was bug 852650 with the same buld log but decompressed. (In reply to Michał Górny from comment #3) > I've also tried a 300 MiB file now. Took a while but eventually big red > error showed. I tried to attach this same file to this bug and now I see this big red error. So I am not sure what was the actual cause, I only see that I repeatedly could not create that bug with HTTP 500 but after having compressed the attachment the creation succeed. Did you have read access to that file? Web browsers tend to badly handle permission errors, so it's possible that your browser sent some junk to the server instead. (In reply to Michał Górny from comment #6) > Did you have read access to that file? Web browsers tend to badly handle > permission errors, so it's possible that your browser sent some junk to the > server instead. It's difficult for me to be 100% sure. I hope I gave proper permissions to the file but admittedly I was extremely tired when was opening that bug and there were many log files, I could mistakenly chmod one and tried to attach another. I experimented and reproduced HTTP 500 when removed read permission from the file. Let me close the bug assuming it was my mistake. I am sorry about noise I created. Don't worry, it's not your fault. It's browser vendors not caring for multiuser systems and failing to implement error handling. |