Develop Reference

How to use ajax for send data to api action in another project

i acan use ajax and api action in one project and send data and update data correctly.
but when i want to send data from ajax in my project to api action in my another project,the api action dont work!
$.ajax({
type: "post",
url: urll,
error: function() {
alert("errore")
},
data: {
id: 4
},
success: function(dataa) {
alert("ok");
var x = JSON.stringify(dataa, null, '\t');
var dataaa = $.parseJSON(x);
alert(dataaa.price);
dataa.price -= 1.02;
var url2 = 'https://localhost:44337/api/apiialbums/PutAlbum';
//var url2 = 'http://localhost:51111/api/AlbumsApi/PutAlbum';
$.ajax({
type: "PUt",
//async: false,
url: url2,
//data: JSON.stringify(dataa, null, '\t'),
data: {
album: dataa
},
//contentType: "application/json; charset=utf-8", ///////
//dataType:"json",
success: function(dataaz) {
alert("updated");
alert(dataaz.price);
var x2 = JSON.stringify(dataaz, null, '\t');
alert(x2);
},
error: function() {
alert("error in update..");
}
})
}
});
and my api [httpput]action:
[HttpPut]
public async Task<ActionResult<Album>> PutAlbum([FromBody]Album album)
{
_context.Entry(album).State = EntityState.Modified;
await _context.SaveChangesAsync(); return album;
}
when i breakpoint in api action,
I understand that the program does not refer to the action
I searched the internet a lot but I could not find the reason, please help me to solve this problem as soon as possible

It's quite probable that you haven't enabled cross-origin requests. As it is stated here:
Browser security prevents a web page from making AJAX requests to another domain. This
restriction is called the same-origin policy, and prevents a malicious
site from reading sensitive data from another site. However, sometimes
you might want to let other sites call your web API.
So you have to enable first Cors. For that reason, you should go in the WebConfig class of the WebAPI that you want to be called and put the following line anywhere inside the Register method:
config.EnableCors();
Then you should go the controller, in which the PutAlbum is defined and decorate with the following attribute
[EnableCors(origins: "http://mywebclient.azurewebsites.net", headers: "*", methods: "PUT")]
You should replace "http://mywebclient.azurewebsites.net" with the URI of your Web Application, that you want to call your Web API.
UPDATE
The above apply for ASP.NET projects. For ASP.NET Core please have a look at here.

in my asp.net core project, i use following code in ConfigureServices in startup:
services.AddCors(options =>
{
options.AddPolicy(MyAllowSpecificOrigins,
builder =>
{
builder.WithOrigins("*")/*.AllowAnyOrigin()*/.AllowAnyHeader().AllowAnyMethod();
});
});
in we can use the client url instead of * :
.WithOrigins("http://localhost:51111")
and in startup in Configure use :
<pre> app.UseCors();</pre>

Handling Twilio response with Sharepoint

I am working with TWILIO and Sharepoint 2016 to send text messages. I have created a Studio Dashboard to send the text messages and a Twilio function to send a response back to a Sharepoint list. My website is external facing with FBA accounts
All of this works if I paste the FEDAUTH code in my function. My question is how do I get the FEDAUTH code ? The pasted FEDAUTH seems to expire after awhile.
exports.handler = function(context, event, callback) {
var options = {
"method": "GET",
"hostname": "www.mysite.org",
"port": null,
"path": "/_layouts/15/Login.aspx",
"headers": {
"authorization": xxxx,
"content-type": "application/x-www-form-urlencoded",
"cache-control": "no-cache",
}
};
var req = http.request(options, function(res) {
var chunks = [];
res.on("data", function(chunk) {
chunks.push(chunk);
});
res.on("end", function() {
var body = Buffer.concat(chunks);
sendAPI();// passed FEDAUTH to /_api/contextinfo/
});
});
req.end();
};

How to pinpoint serialisation errors on Web API endpoints?

At times I have an endpoint on my web api:
[HttpPost]
public async Task Foo([FromForm] int[] a, [FromForm] int b, ...) {
await Task.Delay(1000);
}
When calling this from the client side using axios:
var formData = new FormData();
formData.append('a', this.selected.map(n => n.id));
formData.append('b', this.id);
await this.axios.post('/api/v1/foo', formData);
I get a 400 error. Which states in no way of which field caused the issue. Is there a way of finding out other than trial and error?
POST https://localhost:5001/api/v1/foo 400 (Bad Request)

For Asp.Net Core Api, if you check the web browser network tab, you will see below which already return the expected error response.
{
"errors": {
"a": [
"The value '1,2,3' is not valid."
]
},
"title": "One or more validation errors occurred.",
"status": 400,
"traceId": "8000001e-0004-fe00-b63f-84710c7967bb"
}
If you want to capture the errors by axios, you could try
var formData = new FormData();
formData.append('a', "1,2,3");
formData.append('b', "1");
axios.post('/api/values/Foo', formData)
.then(function (response) {
console.log(response);
})
.catch(function (error) {
console.log(JSON.stringify(error.response.data.errors));
});

ASP.NET: Webmethos does not return payload when http status is 4xx

I have the following code:
[WebMethod]
[ScriptMethod(ResponseFormat = ResponseFormat.Json)]
public static MyResponse myMethod(ParameterClass parameters)
{
MyResponse resp = new MyResponse();
resp.errors.Add("Some error message");
HttpContext.Current.Response.StatusCode = 400;
return resp;
}
running this with jQuery.ajax using url MyPage.aspx/myMethod this call does not return my payload from MyResponse object. Once i switch the statuscode to 200 the return works using the success callback in ajax, but i want to return custom error messages with 4xx and 5xx status codes, how to make it work.
It looks like IIS is the problem, but what do i have to do to still allow returning my class objects on error?
Update 1: i also watched network tab in chrome, IIS is not returning the payload at all, so jQuery cannot be the problem.
Update 2: my jquery ajax call
$.ajax({
url: 'MyPage.aspx/myMethod',
data: JSON.stringify({ parameters: request }),
dataType: "json",
type: "POST",
contentType: "application/json; charset=utf-8",
success: function (data) {
...
},
error: function (data) {
// data.responseJSON is undefined and data.responseText contains only HTTP status code text, like "Bad Request" when code was 400.
}
});

Ok found it in another stackoverflow post.
The solution was to add the following to web.config:
<httpErrors errorMode="DetailedLocalOnly" existingResponse="PassThrough" >
<clear/>
</httpErrors>
By default IIS is replacing the response on error, here the attribute "existingResponse=PassThrough" is the key. Now responseJSON and responseText is filled with my custom content returned by the webmethod.
Found in HttpResponseMessage content lost when HTTP Status is Bad Request

Forms Authentication - token send to controller

When I send this token to Controller in WebApi I get information 401 (Unauthorized) Why? I take this token form login and it`s correct.
$scope.expiresCookie = $cookies.get('expires');
$scope.issuedCookie = $cookies.get('issued');
$scope.access_tokenCookie = $cookies.get('access_token');
$scope.expires_inCookie = $cookies.get('expires_in');
$scope.token_typeCookie = $cookies.get('token_type');
$scope.user_nameCookie = $cookies.get('user_name');
$scope.addLink = "http://localhost:56305/api/ProductInsuranceCar";
$http({
method: "GET",
url: $scope.addLink,
headers: { 'Authorization': '' + $scope.token_typeCookie + ' ' + $scope.access_tokenCookie + '' },
headers: { 'Content-Type': 'application/json; charset=utf-8' }
}).then(function mySucces(response) {
$scope.test = response;
}, function myError(response) {
});
Picture 1
Picture 2
Example correct request
When I use Advanced Rest Client I get information but in my method :/ not working...

Correct answer. Position of header is important :/
headers: { 'Content-Type': 'application/json; charset=utf-8' },
headers: { 'Authorization': $scope.Authorization2 }

The problem could be when calling web api from a different UI domain.
Cookies are not sent if domains are different. So, If you call from localhost:64757 to localhost:56305 cookies are not sent, that's why you are receiving Unathorized 401 error.