Requests to instance-containing visual.force.com hostnames that use an installed managed package (instead of 'c') show a Data Not Found 500 error
Last updated 2020-02-05 ·Reference W-6591291 ·Reported By 0 users
Requests to instance-less orgs that use an instance-containing visual.force.com hostname for an installed managed package show a Data Not Found 500 error instead of redirecting to the instance-containing hostname when the request is processed by an instance that isn't the org's instance.
Requests for these hostnames that go to the correct instance do work. It's odd that 'c' works and not installed managed packages, since the relevant code is supposed to ignore the managed package part and instead focus on the My Domain name. This also works with orgs that aren't yet instance-less.
Example hostnames that don't redirect properly (curl commands provided) and instead return a Data Not Found error with an HTTP-500 response:
curl -v -H "Host: aloha--cms.na45.visual.force.com" https://gs0.force.com/apex/Cats
Using 'c', however, works:
curl -v -H "Host: aloha--c.na45.visual.force.com" https://gs0.force.com/apex/Cats
Using the correct instance also works:
curl -v -H "Host: aloha--cms.na45.visual.force.com" https://na52.force.com/apex/Cats
Reported By (0)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.