Project

General

Profile

Bug #23039

abort early if frontends signal an initialization error

Added by Abhishek Lekshmanan about 6 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
High
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
luminous, jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Since some frontends like civetweb can signal an error if non compliant HTTP Headers are passed on request, abort early in these cases and do not process the request.


Related issues

Copied to rgw - Backport #23107: luminous: abort early if frontends signal an initialization error Resolved
Copied to rgw - Backport #23274: jewel: abort early if frontends signal an initialization error Resolved

History

#1 Updated by Abhishek Lekshmanan about 6 years ago

  • Status changed from New to In Progress
  • Priority changed from Normal to High

#2 Updated by Abhishek Lekshmanan about 6 years ago

  • Assignee set to Abhishek Lekshmanan
  • Backport set to luminous

#3 Updated by Abhishek Lekshmanan about 6 years ago

Suse security assigned CVE-2018-7262 to this

#4 Updated by Abhishek Lekshmanan about 6 years ago

  • Copied to Backport #23107: luminous: abort early if frontends signal an initialization error added

#5 Updated by Casey Bodley about 6 years ago

  • Status changed from In Progress to Pending Backport

#6 Updated by Ken Dreyer about 6 years ago

  • Backport changed from luminous to luminous, jewel

#7 Updated by Abhishek Lekshmanan about 6 years ago

  • Copied to Backport #23274: jewel: abort early if frontends signal an initialization error added

#8 Updated by Nathan Cutler almost 6 years ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF