Project

General

Profile

Bug #12780

Do not store response when response code is an error in file_fom_http_server

Added by Alexis MOUSSET almost 2 years ago. Updated 6 months ago.

Status:
Released
Priority:
N/A
Category:
Generic methods - File Management
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Small
Priority:
0

Description

Currently, if the server responses with an error (404 for example), the error page will be stored and even if the file gets added, it will never be updated.

We should never store the result of a 4** or 5** response and retry until we get a successful response.

#1

Updated by Benoît PECCATTE almost 2 years ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
  • Priority changed from 0 to 52
#2

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 4.1.13 to 4.1.14
#3

Updated by Benoît PECCATTE almost 2 years ago

  • Target version changed from 4.1.14 to 4.1.15
  • Priority changed from 52 to 51
#4

Updated by Alexis MOUSSET over 1 year ago

  • Effort required set to Small
  • Priority changed from 51 to 64
#5

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 4.1.15 to 4.1.16
#6

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 4.1.16 to 4.1.17
  • Priority changed from 64 to 63
#7

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 4.1.17 to 4.1.18
  • Priority changed from 63 to 0
#8

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 4.1.18 to 4.1.19
#9

Updated by Alexis MOUSSET over 1 year ago

  • Target version changed from 4.1.19 to 4.1.20
#10

Updated by François ARMAND about 1 year ago

  • Target version changed from 4.1.20 to 4.1.21
#11

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 4.1.21 to 4.1.22
#12

Updated by Benoît PECCATTE about 1 year ago

  • Target version changed from 4.1.22 to 5.0.10
#13

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 5.0.10 to 5.0.11
#14

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 5.0.11 to 5.0.12
#15

Updated by Vincent MEMBRÉ 11 months ago

  • Target version changed from 5.0.12 to 5.0.13
#16

Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 5.0.13 to 5.0.14
#17

Updated by Vincent MEMBRÉ 8 months ago

  • Target version changed from 5.0.14 to 5.0.15
#18

Updated by Félix DALLIDET 7 months ago

  • Status changed from New to In progress
  • Assignee set to Félix DALLIDET
#19

Updated by Félix DALLIDET 7 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Félix DALLIDET to Alexis MOUSSET
  • Pull Request set to https://github.com/Normation/ncf/pull/1103
#20

Updated by Félix DALLIDET 7 months ago

  • Status changed from Pending technical review to Pending release
#25

Updated by Vincent MEMBRÉ 6 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.15 which was released today.

Also available in: Atom PDF