3 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
2
Note AWS team this is being reported by Penetration Testing firms as an information disclosure vulnerability. Request that action is taken to address..
con risposta 8 mesi fa
0
Unfortunately, there is no option to remove the header at this time. If you deploy 3rd Party Solution like F5 WAF, you can cloak server information.
con risposta un anno fa
Can we hide or change that awselb/2.0 to other name.
0
It's not customizable at the moment. A workaround would be to front the ALB with CloudFront and use edge functions to override the Server
header with none, as briefly illustrated here: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-examples.html#lambda-examples-overriding-response-header
con risposta un anno fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
Same on our side. AWS team please prioritize it.