You may need to update your origin configuration

If you're using your own custom origin to house your content for delivery, you may need to update it to work with your OD property. (For example, you might need to modify infrastructure settings such as session stickiness and load balancing.)

If you are using NetStorage as your origin server, the processes explained here do not apply.

Disable the origin server access control list (ACL)

Note: You can skip this if you do not have a client request access control list (ACL) on your origin servers.

If you have a client IP-based ACL on your origin servers, you need to disable it before beginning delivery of your content or application through the Edge network. Once your application is delivered through the Edge network, your origin servers will no longer see the real client IP addresses and will block all requests. If you need to maintain a client IP ACL, you can specify the list in your Edge server configuration.

Make sure you're using compatible load balancing

Not all load-balancing algorithms are compatible with content delivery services. Incompatible systems include those based on client IP addresses, SSL session identifiers, or least-used connections to specific servers.

This is because more than one Edge server can accept end-user requests in the same session and then forward them to the origin server, which may then see the different Edge servers as different clients. In addition, your origin server will receive requests from a much smaller number of clients, once you switch to the Edge network, as the requests are routed through Edge servers.

If you’ve been using load balancing based on client IP addresses or least-used connections, you need to change the load balancing algorithm when using the Edge network. Compatible algorithms are random or round-robin load distributions replicating session data across all Origin Servers.

Adjust your intrusion detection settings

Using Edge network services may trigger aggressively configured intrusion detection systems. This happens because requests from many end-users are aggregated through a smaller number of Edge servers, potentially making it seem like a single end user is making multiple requests for the same content.