[BO] Erreurs liste des signalements #3398
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
emilschn
approved these changes
Dec 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ticket
#3397
Description
La solution appliqué sur cet PR a introduit une régression dans l'affichage de la liste avec certains filtres, notamment sur le widget "nouveau suivi".
Le problème vient de la quantité d'information stockée dans le cookie. Contrairement à la session qui n'a pas de limite de taille intrinsèque (ça va dépendre du redis nous concernant), les cookies sont limités par la taille totale des en-têtes HTTP, ce qui peut causer des erreurs serveur lorsque trop d'informations sont envoyés.
2024-12-04T17:22:55.237901707Z 2024/12/04 17:22:55 [error] 43#43: *94 upstream sent too big header while reading response header from upstream, client: 172.20.0.1, server: , request: "GET /bo/list/signalements/?sortBy=lastSuiviAt&direction=DESC&nouveauSuivi=oui HTTP/1.1", upstream: "fastcgi://172.20.0.8:9000", host: "localhost:8080"Augmenter la taille des en-têtes côté nginx corrigera le problème pour quelques temps donc mieux vaut ne pas stocker le contenu des filtres dans le cookie.
Changements apportés
Pré-requis
Tests