The following will server up the net storage page, however it returns a 200 response code, not a 404 as set.
You are still getting 200 because once you do Site Failover to Netstorage domain, none of the rule in your existing configuration will apply. When the site is failover to Netstorage, Edge will create request to netstorage domain and will get the content from netstorage and will serve it to end user without parsing any of the rule in your configuration. The configuration is not configured to reset the response code to 404 once the content is received from netstorage.
We have achieved this kind of functionality when the site is failing over to origin-DR site or another page under same domain. With this setup, i think you need some additional setup.
1. Create failover-domain let's say failover-test.edgesuite.net. You can create new edgesuite domain from the portal.
2. Add failover-test.edgesuite.net in your existing configuration
3. You need to change origin configuration for your failover-test.edgesuite.net,
4. Once you do this, Your failover request will get parsed by this configuration.
5. Just add one more match on your ModifyPath rule like below
6. When the request gets triggered for your failover domain, this rule will set the response to 404 after receiving the content from netstorage.
This might be a little difficult to configuration but in case you need any help, I recommend you to work with Akamai Customer Care for any assistance.
Hi Chris Raheb Could you try matching on the modified path URL? What I think is happening is that the page coming from NetStorage is taken as a 200 and not entering your match on 404. You need to put the rule outside the match on response code 404 and match on the modified URL path.
When you use Site Failover the retry is taking as a new request
Let me know if that fix it
So you're saying create a new rule? then add a match on modified path URL to my html file, then set the behaviour of 404 there?
I don't see a way to match modified path URL.
Yes, a new rule. In my text I used the word modified path when referring to the actual URL path, not the property manager interface.
Something like this
That is outside the match on response 404
If i go to example.com/asdfasdf, akamai will server up the contents of net storage.
Wouldn't the path be /asdfasdf, not /modified/path/404.html
I have tested this and it is still returning a 200.
Yes. You need to match on your NetStorage path. The path I used is an example
I set it to the net storage path, but it is still returning a 200.
My question was, if we are setting the path to net storage, does that make sense?
Isn't the path going to be /asdfasdf if i go to example.com/asdfasdf, not the net storage path?
Were you able to achieve desired results?
Retrieving data ...