Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Fortinet Exam NSE6_FWB-6.4 Topic 1 Question 54 Discussion

Actual exam question for Fortinet's NSE6_FWB-6.4 exam
Question #: 54
Topic #: 1
[All NSE6_FWB-6.4 Questions]

Which would be a reason to implement HTTP rewriting?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Fallon
6 days ago
Haha, I bet the correct answer is something really obvious that we're all overthinking. My money's on A - the original page has moved to a new URL, so rewriting the request makes sense.
upvoted 0 times
...
Jose
10 days ago
Hmm, I'm not sure. The question is a bit tricky. Maybe D? If the page has moved to a new IP address, rewriting the URL could be a solution.
upvoted 0 times
...
Paola
16 days ago
I'm going with B. Replacing a vulnerable function in the URL is a security best practice, and HTTP rewriting can be used to achieve that.
upvoted 0 times
...
Desmond
20 days ago
Option C seems like the right choice here. Redirecting the request to a secure channel is a common reason for implementing HTTP rewriting.
upvoted 0 times
...
Kiera
22 days ago
Hmm, that makes sense too. It's important to ensure security when transmitting data.
upvoted 0 times
...
Yuki
23 days ago
I disagree, I believe it's to send the request to a secure channel.
upvoted 0 times
...
Kiera
26 days ago
I think the reason to implement HTTP rewriting is to replace a vulnerable function in the requested URL.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77