关于“Configuring Traffic Blocklisting with Google Cloud Armor”的评价

Jónatan L. · 已于 almost 4 years前审核

Thanos G. · 已于 almost 4 years前审核

Muhammad A. · 已于 almost 4 years前审核

Zakaria B. · 已于 almost 4 years前审核

Sharez S. · 已于 almost 4 years前审核

s p. · 已于 almost 4 years前审核

Joe S. · 已于 almost 4 years前审核

Pete M. · 已于 almost 4 years前审核

Abhinav S. · 已于 almost 4 years前审核

Neil P. · 已于 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. · 已于 almost 4 years前审核

NICOLAS D. · 已于 almost 4 years前审核

Daniel A. · 已于 almost 4 years前审核

Samir R. · 已于 almost 4 years前审核

Jose Ignacio S. · 已于 almost 4 years前审核

Kevin N. · 已于 almost 4 years前审核

Elron John T. · 已于 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. · 已于 almost 4 years前审核

Andreja A. · 已于 almost 4 years前审核

Sathish Kumar G. · 已于 almost 4 years前审核

Максим K. · 已于 almost 4 years前审核

Jacky F. · 已于 almost 4 years前审核

nice

Maha L. · 已于 almost 4 years前审核

Roma Ś. · 已于 almost 4 years前审核

Joseph I. · 已于 almost 4 years前审核