Bug 1512911 - Internal server Error on incorrect headers
Summary: Internal server Error on incorrect headers
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: AAA
Version: future
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.2.0
: 4.2.0
Assignee: Ravi Nori
QA Contact: Gonza
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-14 12:24 UTC by Michal Skrivanek
Modified: 2017-12-22 06:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-22 06:50:50 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.2+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 84966 0 master MERGED aaa: Internal server Error on incorrect headers 2020-02-24 07:07:53 UTC

Description Michal Skrivanek 2017-11-14 12:24:59 UTC 
Engine is raising internal server error in case of invalid headers. This might be a problem for older API clients and it's not nice to flood the logs in any case

See issue for older clients reported in https://github.com/oVirt/ovirt-web-ui/issues/400
Comment 1 Sandro Bonazzola 2017-12-12 16:06:45 UTC 
This bug is targeted 4.2.1 but is modified in 4.2.0.
Can you please check / verify this bug status and set target milestone and bug status accordingly?
Comment 2 Martin Perina 2017-12-12 18:21:36 UTC 
Moving to 4.2.0 as it's part of latest build
Comment 3 Gonza 2017-12-21 09:59:41 UTC 
Verified with:
ovirt-engine-4.2.0.2-0.1.el7.noarch
Comment 4 Sandro Bonazzola 2017-12-22 06:50:50 UTC 
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.