Disable Abuse Checking on REST Requests

Former Member — Tue, 04 Aug 2020 18:06:07 GMT

Current Revision posted to Developer Training by Former Member on 08/04/2020 18:06:07

When creating or updating content that implements the IAbuseCheckingContentType content is detected by the individual abuse detectors that handle events applicable to their abuse detection logic and notify the abuse service when abuse is detected. Using the header "Rest-Disable-AbuseChecking" with the value "True" will bypass any abuse detectors that check if the content that is being created or updated is exempt via the IAbuseController IsExempt value. If using API key authentication via REST, the user making the REST request must have the "Manage Site" permission. If using OAuth authentication, the user making the REST request must have the OAuth Permission "Manage Settings".

[TOC]

Why Should I Disable Abuse Checking When Using REST

If you're migrating existing content from another system, you may not wish for that content to go through any type of abuse checking.

Making a REST Request with Abuse Checking Disabled

var request = WebRequest.Create("https://myverintcommunitysite.com/api.ashx/v2/info.json") as HttpWebRequest;
request.Method = "Get";

// replace the "admin" and "Admin's API key" with your valid user and apikey!
var adminKey = String.Format("{0}:{1}", "Admin's API key", "admin");
var adminKeyBase64 = Convert.ToBase64String(Encoding.UTF8.GetBytes(adminKey));

request.Headers.Add("Rest-User-Token", adminKeyBase64);
request.Headers.Add("Rest-Disable-AbuseChecking", "True");

var response = request.GetResponse() as HttpWebResponse;

Disable Abuse Checking on REST Requests

Brian Dooley — Thu, 29 Aug 2019 15:34:35 GMT

Revision 4 posted to Developer Training by Brian Dooley on 08/29/2019 15:34:35

[TOC]

Why Should I Disable Abuse Checking When Using REST

If you're migrating existing content from another system, you may not wish for that content to go through any type of abuse checking.

Making a REST Request with Abuse Checking Disabled

var request = WebRequest.Create("https://mytelligentcommunitysite.com/api.ashx/v2/info.json") as HttpWebRequest;
request.Method = "Get";

// replace the "admin" and "Admin's API key" with your valid user and apikey!
var adminKey = String.Format("{0}:{1}", "Admin's API key", "admin");
var adminKeyBase64 = Convert.ToBase64String(Encoding.UTF8.GetBytes(adminKey));

request.Headers.Add("Rest-User-Token", adminKeyBase64);
request.Headers.Add("Rest-Disable-AbuseChecking", "True");

var response = request.GetResponse() as HttpWebResponse;

Disable Abuse Checking on REST Requests

Brian Dooley — Tue, 27 Aug 2019 13:58:38 GMT

Revision 3 posted to Developer Training by Brian Dooley on 08/27/2019 13:58:38

When creating or updating content that implements the IAbuseCheckingContentType content is detected by the individual abuse detectors that handle events applicable to their abuse detection logic and notify the abuse service when abuse is detected. Using the header "Rest-Disable-AbuseChecking" with the value "True" will bypass any abuse detectors that check if the content that is being created or updated is exempt via the IAbuseController IsExempt value. The user making the REST request must have the "Manage Site" permission.

[TOC]

Why Should I Disable Abuse Checking When Using REST

If you're migrating existing content from another system, you may not wish for that content to go through any type of abuse checking.

Making a REST Request with Abuse Checking Disabled

var request = WebRequest.Create("https://mytelligentcommunitysite.com/api.ashx/v2/info.json") as HttpWebRequest;
request.Method = "Get";

// replace the "admin" and "Admin's API key" with your valid user and apikey!
var adminKey = String.Format("{0}:{1}", "Admin's API key", "admin");
var adminKeyBase64 = Convert.ToBase64String(Encoding.UTF8.GetBytes(adminKey));

request.Headers.Add("Rest-User-Token", adminKeyBase64);
request.Headers.Add("Rest-Disable-AbuseChecking", "True");

var response = request.GetResponse() as HttpWebResponse;

Disable Abuse Checking on REST Requests

Brian Dooley — Mon, 01 Jul 2019 14:35:11 GMT

Revision 2 posted to Developer Training by Brian Dooley on 07/01/2019 14:35:11

[TOC]

Why Should I Disable Abuse Checking When Using REST

If you're migrating existing content from another system, you may not wish for that content to go through any type of abuse checking.

Making a REST Request with Abuse Checking Disabled

var request = WebRequest.Create("https://mytelligentcommunitysite.com/api.ashx/v2/info.json") as HttpWebRequest;
request.Method = "Get";

// replace the "admin" and "Admin's API key" with your valid user and apikey!
var adminKey = String.Format("{0}:{1}", "Admin's API key", "admin");
var adminKeyBase64 = Convert.ToBase64String(Encoding.UTF8.GetBytes(adminKey));

request.Headers.Add("Rest-User-Token", adminKeyBase64);
request.Headers.Add("Rest-Disable-AbuseChecking", "True");

var response = request.GetResponse() as HttpWebResponse;

Disable Abuse Checking on REST Requests

Brian Dooley — Fri, 28 Jun 2019 19:40:19 GMT

Revision 1 posted to Developer Training by Brian Dooley on 06/28/2019 19:40:19

[TOC]

Why Should I Disable Abuse Checking When Using REST

If you're migrating existing content from another system, you may not wish for that content to go through any type of abuse checking.

Making a REST Request with Abuse Checking Disabled

var request = WebRequest.Create("https://mytelligentcommunitysite.com/api.ashx/v2/info.json") as HttpWebRequest;
request.Method = "Get";

// replace the "admin" and "Admin's API key" with your valid user and apikey!
var adminKey = String.Format("{0}:{1}", "Admin's API key", "admin");
var adminKeyBase64 = Convert.ToBase64String(Encoding.UTF8.GetBytes(adminKey));

request.Headers.Add("Rest-User-Token", adminKeyBase64);
request.Headers.Add("Rest-Disable-AbuseChecking", "True");

var response = request.GetResponse() as HttpWebResponse;