Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 852647 - https://bugs.gentoo.org: POST /post_bug.cgi: 500 Internal server error
Summary: https://bugs.gentoo.org: POST /post_bug.cgi: 500 Internal server error
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Infrastructure
Classification: Unclassified
Component: Bugzilla (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Bugzilla Admins
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-06-16 21:43 UTC by Alexander Bezrukov
Modified: 2022-06-18 05:57 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Bezrukov 2022-06-16 21:43:22 UTC 
I am trying to file a bug in bugzilla (in Gentoo Linux / current packages component) and reproducibly receive HTTP Error 500.

My IP is 94.231.166.93, timestamp is Thu Jun 16 09:42:52 PM UTC 2022
Comment 1 Alexander Bezrukov 2022-06-16 21:52:25 UTC 
It seems that I see the problem: a too large attachment.
Anyway, a more informative error message would be helpful.
Comment 2 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2022-06-17 04:09:45 UTC 
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.
Comment 3 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2022-06-17 04:13:09 UTC 
I've also tried a 300 MiB file now.  Took a while but eventually big red error showed.
Comment 4 Alexander Bezrukov 2022-06-17 15:56:50 UTC 
(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.
Comment 5 Alexander Bezrukov 2022-06-17 16:03:35 UTC 
(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.
Comment 6 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2022-06-17 19:05:32 UTC 
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.
Comment 7 Alexander Bezrukov 2022-06-17 20:11:17 UTC 
(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.
Comment 8 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2022-06-18 05:57:41 UTC 
Don't worry, it's not your fault.  It's browser vendors not caring for multiuser systems and failing to implement error handling.