The problem is probably due to the fact that razor pages automatically check for the RequestVerificationToken, assuming a form-driven post. I found it necessary to do the following:
1. Add a property & constructor to the pagemodel to receive the anti-forgery injection:
public IAntiforgery Xsrf { get; private set; }
public MyPageModel(IAntiforgery xsrf)
{
Xsrf = xsrf;
}
2. Declare a property on the pages' codebehind:
public List> Headers
{
get
{
var hdr = new List>();
var dict = new Dictionary
{
["RequestVerificationToken"] = Xsrf.GetAndStoreTokens(HttpContext).RequestToken
};
hdr.Add(dict);
return hdr;
}
}
3. In the datamanager tag helper, add a "headers" attribute:
insert-url="/Content/Insert"
remove-url="/Content/Remove"
update-url="/Content/Update"
adaptor="remoteSaveAdaptor"
headers=@Model.Headers />
This will send the token as part of the header to any of the CRUD requests, and you should see the handlers firing.
Also, make sure you have
@page "{handler?}"
at the top of your cshtml so that it knows to route the extra handlers. (see the link that Steven posted for more info)
