Como configurar listas de bloqueio de tráfego com o Google Cloud Armor avaliações

Jónatan L. · Revisado há almost 4 years

Thanos G. · Revisado há almost 4 years

Muhammad A. · Revisado há almost 4 years

Zakaria B. · Revisado há almost 4 years

Sharez S. · Revisado há almost 4 years

s p. · Revisado há almost 4 years

Joe S. · Revisado há almost 4 years

Pete M. · Revisado há almost 4 years

Abhinav S. · Revisado há almost 4 years

Neil P. · Revisado há almost 4 years

I tried 3 times to get the 404 status code, it worked on the third time, nothing surprising so far as it is mentioned in the lab notes. However, even though I got a single 404 response with curl, but I could see 3 entries with very different timestamps (~10 seconds apart) in the logs that I got a 404 response. The remote ip did match my VM for all 3 entries. So, they must correspond to my 3 attempts mentioned earlier. I think there might be a bit of a bug between what actually happened and what the load balancer logs say happened.

NICOLAS F. · Revisado há almost 4 years

NICOLAS D. · Revisado há almost 4 years

Daniel A. · Revisado há almost 4 years

Samir R. · Revisado há almost 4 years

Jose Ignacio S. · Revisado há almost 4 years

Kevin N. · Revisado há almost 4 years

Elron John T. · Revisado há almost 4 years

the deny rule is priority 1000 while the allow is 2,147,483,647. The acces-test vm will never get 404 deny

Valentin V. · Revisado há almost 4 years

Andreja A. · Revisado há almost 4 years

Sathish Kumar G. · Revisado há almost 4 years

Максим K. · Revisado há almost 4 years

Jacky F. · Revisado há almost 4 years

nice

Maha L. · Revisado há almost 4 years

Roma Ś. · Revisado há almost 4 years

Joseph I. · Revisado há almost 4 years