Which of the following are correct request methods when configuring a URL filtering rule with a Caution action?

In Zscaler's URL Filtering policy, the Caution action presents an End-User Notification (EUN) page warning users about potentially risky destination websites before granting access. Because presenting an interactive HTML warning page and processing a user's click-through response requires safe, standard web request methods, Zscaler restricts the Caution action specifically to the CONNECT, GET, and HEAD HTTP request methods. Methods such as POST, PUT, DELETE, and TRACE involve uploading payloads, modifying resources, or diagnostic tracing where inserting an interactive EUN page could break application logic or result in unsafe data submissions. Therefore, configuring Caution is only supported for the standard retrieval and tunnel setup methods: CONNECT, GET, and HEAD.

Option B: OPTIONS, DELETE, and PUT methods perform state-changing or capability query operations where interactive End-User Notification caution pages cannot be safely rendered.

Option C: TRACE and DELETE request methods do not support interactive user browser prompting required for the Caution action EUN display.

Option D: POST and PUT methods carry request payloads that could be prematurely transmitted or broken when intercepted by an interactive caution page.

- Zscaler Documentation: "Configuring URL Filtering Policy", Zscaler Help Portal, Section: "URL Filtering Policy Actions and HTTP Request Methods".

- Zscaler Documentation: "URL Filtering Policy Settings", Section: "Actions - Caution".