id summary reporter owner description type status priority milestone component version severity resolution keywords cc focuses 39889 Improve/Fix REST Response on Multisite when an endpoint for a non-existent site is hit. nerrad "Currently if you hit the endpoint for a domain on a site that doesn't exist it will behave the same as on a normal request. - visit https://nonexistentsubdomain.eventsmart.com/wp-json in a REST client. - Take note of the ""Location"" header in the response: https://eventsmart.com/wp-signup.php?new=nonexistentsite. It's also returned with a HTTP 302 Granted this is kind of edgecase, but I think it'd be better to handle things a bit better on REST requests. The question is how? I think from the standpoint of the REST client it'd be better to just return a 404 and a ""site doesnt' exist"" message (or something to that affect)." defect (bug) new normal Future Release REST API 4.7 normal needs-patch needs-unit-tests multisite, rest-api