Question: When TLS security is negotiated between two SBA Security Edge Protection Proxies (SEPPs) and both indicate support for the `3gpp-Sbi-Target-apiRoot` header, how does the sending SEPP handle the `apiRoot` in the HTTP Request when forwarding messages to the receiving SEPP?
Option 1: The sending SEPP appends the `apiRoot` of the receiving SEPP to the existing `apiRoot` in the Request URI.
Option 2: The sending SEPP replaces the `apiRoot` of the Request URI with the `apiRoot` of the receiving SEPP before forwarding the HTTP Request.
Option 3: The sending SEPP removes the `apiRoot` from the Request URI and forwards the HTTP Request without an `apiRoot`.
Option 4: The sending SEPP leaves the `apiRoot` in the Request URI unchanged when forwarding the HTTP Request.
Explanation: When both SEPPs support the `3gpp-Sbi-Target-apiRoot` header and TLS security is negotiated, the sending SEPP must ensure the `apiRoot` points to the receiving SEPP for correct routing. Thus, it replaces the original `apiRoot` with that of the receiving SEPP, ensuring seamless communication between the NF services across different domains.