"Help -> Report a Bug" throws "400 Bad Request" message #68156

Closed
opened 2019-08-03 01:03:45 +02:00 by rudy serna · 21 comments

System Information
Operating system: macOS High Sierra
Graphics card:

Blender Version
Broken: 2.80 2019-07-19
Worked: (optional)

tried to submit a bug report using "Help -> Report a Bug" and received an error message "400 Bad Request"

Exact steps for others to reproduce the error - - try submitting a bug request using Help...
Based on the default startup or an attached .blend file (as simple as possible).

**System Information** Operating system: macOS High Sierra Graphics card: **Blender Version** Broken: 2.80 2019-07-19 Worked: (optional) tried to submit a bug report using "Help -> Report a Bug" and received an error message "400 Bad Request" **Exact steps for others to reproduce the error** - - try submitting a bug request using Help... Based on the default startup or an attached .blend file (as simple as possible).
Author

Added subscriber: @Rooster

Added subscriber: @Rooster

Added subscriber: @StephenSwaney

Added subscriber: @StephenSwaney
You should report that as a bug. Oh, wait! Happens here too, 2.80 release on Linux url is https://developer.blender.org/maniphest/task/edit/form/1?description=%2A%2ASystem%20Information%2A%2A%0AOperating%20system%3A%20Linux-5.0.0-23-lowlatency-x86_64-with-debian-buster-sid%2064%20Bits%0AGraphics%20card%3A%20GeForce%20GTX%201660/PCIe/SSE2%20NVIDIA%20Corporation%204.5.0%20NVIDIA%20418.56%0A%0A%0A%2A%2ABlender%20Version%2A%2A%0ABroken%3A%20version%3A%202.80%20%28sub%2075%29%2C%20branch%3A%20master%2C%20commit%20date%3A%202019-07-29%2014%3A47%2C%20hash%3A%20%60rBf6cb5f54494e%60%0AWorked%3A%20%28optional%29%0A%0A%0A%2A%2AShort%20description%20of%20error%2A%2A%0A%5BPlease%20fill%20out%20a%20short%20description%20of%20the%20error%20here%5D%0A%0A%2A%2AExact%20steps%20for%20others%20to%20reproduce%20the%20error%2A%2A%0A%5BPlease%20describe%20the%20exact%20steps%20needed%20to%20reproduce%20the%20issue%5D%0A%5BBased%20on%20the%20default%20startup%20or%20an%20attached%20.blend%20file%20%28as%20simple%20as%20possible%29%5D%0A%0A
Member

Added subscriber: @LazyDodo

Added subscriber: @LazyDodo
Member

it's ok until the %0A then it http 400's

it's ok until the %0A then it http 400's
Sergey Sharybin was assigned by Ray molenkamp 2019-08-03 02:00:41 +02:00
Member

Added subscriber: @Sergey

Added subscriber: @Sergey
Member

@Sergey as the local phab guru mind taking a peek here?

@Sergey as the local phab guru mind taking a peek here?
Member

Added subscriber: @Mets

Added subscriber: @Mets
Member

Duplicate of #68147, which might be a duplicate of blender/blender-addons#68007.

Duplicate of #68147, which might be a duplicate of blender/blender-addons#68007.

Added subscriber: @Josephbburg

Added subscriber: @Josephbburg

Happens for me, too, and I don't think it's Blender. I have reported bugs from 2.80 and 2.80 RC3 before, and both are giving me the 400 error right now. It's on the maniphest/phabricator or whatever this site is called.

Happens for me, too, and I don't think it's Blender. I have reported bugs from 2.80 and 2.80 RC3 before, and both are giving me the 400 error right now. It's on the maniphest/phabricator or whatever this site is called.
Member

Added subscriber: @dmcgrath

Added subscriber: @dmcgrath
Member

The logs show:

2019-08-03 04:45:26: (response.c.346) invalid character in URI -> 400 /maniphest/task/edit/form/1?description=%2A%2ASystem%20Information%2A%2A%0AOperating%20system%3A%20Linux-4.15.0-55-generic-x86_64-with-Ubuntu-18.04-bionic%2064%20Bits%0AGraphics%20card%3A%20GeForce%20GTX%20960/PCIe/SSE2%20NVIDIA%20Corporation%204.5.0%20NVIDIA%20390.116%0A%0A%0A%2A%2ABlender%20Version%2A%2A%0ABroken%3A%20version%3A%202.80%20%28sub%2075%29%2C%20branch%3A%20heads/v2.80%20%28modified%29%2C%20commit%20date%3A%202019-07-29%2014%3A47%2C%20hash%3A%20%60rBf6cb5f54494e%60%0AWorked%3A%20%28optional%29%0A%0A%0A%2A%2AShort%20description%20of%20error%2A%2A%0A%5BPlease%20fill%20out%20a%20short%20description%20of%20the%20error%20here%5D%0A%0A%2A%2AExact%20steps%20for%20others%20to%20reproduce%20the%20error%2A%2A%0A%5BPlease%20describe%20the%20exact%20steps%20needed%20to%20reproduce%20the%20issue%5D%0A%5BBased%20on%20the%20default%20startup%20or%20an%20attached%20.blend%20file%20%28as%20simple%20as%20possible%29%5D%0A%0A

The logs show: ``` 2019-08-03 04:45:26: (response.c.346) invalid character in URI -> 400 /maniphest/task/edit/form/1?description=%2A%2ASystem%20Information%2A%2A%0AOperating%20system%3A%20Linux-4.15.0-55-generic-x86_64-with-Ubuntu-18.04-bionic%2064%20Bits%0AGraphics%20card%3A%20GeForce%20GTX%20960/PCIe/SSE2%20NVIDIA%20Corporation%204.5.0%20NVIDIA%20390.116%0A%0A%0A%2A%2ABlender%20Version%2A%2A%0ABroken%3A%20version%3A%202.80%20%28sub%2075%29%2C%20branch%3A%20heads/v2.80%20%28modified%29%2C%20commit%20date%3A%202019-07-29%2014%3A47%2C%20hash%3A%20%60rBf6cb5f54494e%60%0AWorked%3A%20%28optional%29%0A%0A%0A%2A%2AShort%20description%20of%20error%2A%2A%0A%5BPlease%20fill%20out%20a%20short%20description%20of%20the%20error%20here%5D%0A%0A%2A%2AExact%20steps%20for%20others%20to%20reproduce%20the%20error%2A%2A%0A%5BPlease%20describe%20the%20exact%20steps%20needed%20to%20reproduce%20the%20issue%5D%0A%5BBased%20on%20the%20default%20startup%20or%20an%20attached%20.blend%20file%20%28as%20simple%20as%20possible%29%5D%0A%0A ```
Member

An old Blender 2.77 redirects to https://developer.blender.org/maniphest/task/create/?project=2&type=Bug and shows:
Screenshot_2019-08-02_22-49-54.png

An old `Blender 2.77` redirects to `https://developer.blender.org/maniphest/task/create/?project=2&type=Bug` and shows: ![Screenshot_2019-08-02_22-49-54.png](https://archive.blender.org/developer/F7646553/Screenshot_2019-08-02_22-49-54.png)
Member

Looks like a lighttpd error, perhaps relevant?

http://redmine.lighttpd.net/boards/2/topics/8610

Looks like a lighttpd error, perhaps relevant? http://redmine.lighttpd.net/boards/2/topics/8610
Member

I'm wondering if it's:

http://redmine.lighttpd.net/projects/lighttpd/wiki/Server_http-parseoptsDetails

We run 1.4.54, which we just upgraded to, and that page mentions:

  • "method-get-body" => "enable" (since 1.4.54)
    ** permit GET sent with request body (default: reject with 400 Bad Request)
I'm wondering if it's: http://redmine.lighttpd.net/projects/lighttpd/wiki/Server_http-parseoptsDetails We run 1.4.54, which we just upgraded to, and that page mentions: * "method-get-body" => "enable" (since 1.4.54) ** permit GET sent with request body (default: reject with 400 Bad Request)
Member

Okay, seems that specifically it was:

  • server.http-parseopts = ( "url-ctrls-reject" => "disable" )

After a reload, the page loads fine now. The question is, why was that done? The original bug report was one guy asking a valid "WHY", and the other guy taking offense, but not really answering the question, so I really don't know about any consequences of this. That said, I don't feel that we can afford to break bug reporting for every Blender release, do you? :)

I'll leave you guys to close the report, but I will mention that the old 2.77 URL is still broken, so perhaps we should keep it open until we figure out what is going on there, as well.

Okay, seems that specifically it was: * server.http-parseopts = ( "url-ctrls-reject" => "disable" ) After a reload, the page loads fine now. The question is, why was that done? The original bug report was one guy asking a valid "WHY", and the other guy taking offense, but not really answering the question, so I really don't know about any consequences of this. That said, I don't feel that we can afford to break bug reporting for _every_ Blender release, do you? :) I'll leave you guys to close the report, but I will mention that the old 2.77 URL is still broken, so perhaps we should keep it open until we figure out what is going on there, as well.
Author

no sorries - CLOSE it

no sorries - CLOSE it
Author

to LazyDodo; for myself, please close this report - thanks

to LazyDodo; for myself, please close this report - thanks

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

Seems to be fixed now.
Thanks everyone, closing! :)

Seems to be fixed now. Thanks everyone, closing! :)
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
7 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#68156
No description provided.