I got it. I didn't correctly point out Header... I made a mistake in Aplications code - Aplication.

It's very easy to use. https://ru.wikipedia.org/wiki/JSONP ♪ The php beam should give javascript the procedure with the answer: response("data")♪ Then create a violin <script src="jsonp.php?q=response"></script>the response shall be placed on the page in advance. It's a devious way of circumventing CORS.

Because you have a test. if (recept.type === 'cors') {and, accordingly, if the condition is not met (and is not met), no data will be added.Moreover, the panic should initially contain all pages rather than change when the data are downloaded!

As long as the toxic users are not banished, I'll answer your question quickly. The area is functional. Array.proptotype.filterbypassing the force Array.prototype.forEach♪ Don't do anything. for (let key in content) let value = content[key] ES6 is analog. for (let value of content)It's particularly annoying in your code that you're wrong to call variables/functions and...d. getResponse - the answer is what? The code should be read as a book first.list.innerHTML += Forget about this thing! It's just like a tank to run a DOM tree, use it or classic. createElement Or try your powers in React. If you use jQuery, you', of course, hit a stick but usually don't hurt.Working example: https://codepen.io/latdev/pen/yLoqpPx const url = "https://makeup-api.herokuapp.com/api/v1/products.json?brand="; const posts = document.querySelector("#app .posts"); /** Create request for makeup-api.herokuapp.com products, and append .posts @param string brand which brand to search? @returns void */ async function requestMakeupData(brand) { if (typeof(brand) !== "string") throw new Error("argument brand must be an string"); let response = await fetch(url + brand); let products = await response.json(); products .filter(product => parseFloat(product.price) < 5) .forEach(product => { let node = document.createElement("li"); let nodeHeader = document.createElement("h3"); nodeHeader.innerText = product.name; node.append(nodeHeader); let nodeText = document.createElement("p"); nodeText.innerText = product.price; node.append(nodeText); posts.append(node); }) } requestMakeupData("maybelline");

Documentation https://learn.javascript.ru/fetch ♪ response Method jsonLiteracyresponse.json() - decoding response in JSON formatI mean, there's a seal here, and it's got to look like this.async function ReadJsonByHttp(){ let url = 'https://junecat.ru/Storage/Others/data.json'; let response = await fetch(url); let jtxt = await response.json(); // здесь опечатка console.log('response json: ' + JSON.stringify(jtxt)); }

connect-src not clearly defined and applied default-src 'self' (whether with other meanings).You already have Content Security Policy (CSP), so your added metaphors don't work. He just adds the second CSP, but the first one keeps blocking it. That's what you can see on the blocking rules: default-src 'self' 'unsafe-inline' data: - they're from the first CSP, not from your meta theater.So you need to find where the first CSP is published and add the source. http://data.fixer.io It's her.In Prod CSP mode, the electron is published only by metathega.Dev mode (a) http(ws)://localhost:3000 CSP may also be published by HTTP-heading. See if you're not making it. https://stackoverflow.com/questions/64060894/trouble-with-content-security-policy/64068629#64068629 (on the Eng, but only the picture is important.)Check your location code:session.defaultSession.webRequest.onHeadersReceived((details, callback) => { callback({ responseHeaders: Object.assign({ ...details.responseHeaders, "Content-Security-Policy": [ "default-src 'self' 'unsafe-inline' data:" ] }, details.responseHeaders)}); }); He may issue CSP heading in Dev mode. CSP headlines may also issue flames electron-forge and electron-forge/plugin-webpack - They have a CSP set for the development regime (Dev).And check the HTML code for your application in the browser for a second meta tega. <meta http-equiv="Content-Security-Policy"because the flames can publish it and through meta tega. Then the HTML code will be two meta tega, one yours, the other from the flame.Comment. The behavior you describe when adding http(ws)://localhost:3000 - it's a false trail, localhost normally covered by thin 'self'which you have in both CSPs.ws://localhost:3000 only if web-baseds are used, http://csplite.com/ru/csp/test25/ http://localhost:3000♪

Perhaps the problem is you're returning a vocabulary from python, not json object. return flask.jsonify(json_data)I advise you to use ajax. It's easier for me to taste.

async function getApiMiningData() { const response = await fetch( `https://min-api.cryptocompare.com/data/blockchain/mining/calculator?fsyms=BTC,ETH,ZEC&tsyms=USD` ); const result = await response.json(); //this.miningData.push(result.Data); console.log(result.Data); } getApiMiningData();

You have a problem with the parameters of the request, that's an example of the discharge. async function getNews(){ let r = await fetch('https://api.cognitive.microsoft.com/bing/v7.0/news?category=sports&mkt=en-us', { 'Ocp-Apim-Subscription-Key': '123456789ABCDE', 'User-Agent': 'Mozilla/5.0 (compatible; MSIE 10.0; Windows Phone 8.0;Trident/6.0; IEMobile/10.0; ARM; Touch; NOKIA; Lumia 822)', 'X-Search-ClientIP': '999.999.999.999', 'X-Search-Location': 'lat:47.60357;long:-122.3295;re:100', 'X-MSEdge-ClientID': '<blobFromPriorResponseGoesHere>', 'Host': 'api.cognitive.microsoft.com' }) let news = await r.json(); console.log(news) } getNews()But by the end, the error is returning the error 401, so you need to check the signature keys.

No. Unless you make a request synchronized, but in this case, you're blocking the interface.The request should be asynchronous and not slow down the pages. You just need to add, until the answer comes, the jackass... loading♪

EF Core, after adding (INSERT) data to the OBD, immediately obtains (SELECT) ID from it. And in your handle code, I only see INSERT.You have to do that.public async Task<int> CreateDataAsync(FormAbsence model) { if (model == null) return 0; var sqlExpression = "INSERT INTO FormAbsence (reason, start_date, duration, discounted, description) " + "VALUES (@reason, @startDate, @duration, @discounted, @description); " + "SELECT scope_identity();"; using (var connection = new SqlConnection(_context.ConnectString)) { await connection.OpenAsync(); using (var command = new SqlCommand(sqlExpression, connection)) { command.Parameters.Add("reason", SqlDbType.NVarChar).Value = model.Reason; command.Parameters.Add("startDate", SqlDbType.DateTime2).Value = model.StartDate.Date; command.Parameters.Add("duration", SqlDbType.Int).Value = model.Duration; command.Parameters.Add("discounted", SqlDbType.NVarChar).Value = model.Discounted; command.Parameters.Add("description", SqlDbType.NVarChar).Value = model.Description; int id = (int)(decimal)(await command.ExecuteScalarAsync()); model.Id = id; return id; } } } Make sure you use the parametered queries! This will completely eliminate sql injections and increase productivity.I don't know what type you have in the table, so edit yourself. SqlDbType♪Like, I'm not sure about the type coming back. id♪ Tell me the right thing.Your method is returning Task<int> - what does that mean? int? I got it back. idbut it doesn't make much sense. You decide.If the logic is included in EF Core, approximately such a request will be generated when the data are collected (Orders and UserId - the name of the table and columns in my OBD:SET NOCOUNT ON; INSERT INTO [Orders] ([UserId]) VALUES (@p0); SELECT [Id] FROM [Orders] WHERE @@ROWCOUNT = 1 AND [Id] = scope_identity(); As can be seen, immediately after the retrieval, a newly-gen. scope_identity() and this value is returning. And EF Core updates Id In fact.I'll tell you what. https://docs.microsoft.com/en-us/sql/t-sql/functions/scope-identity-transact-sql?view=sql-server-ver15 - this is Sql Server. There's something else to be used in working with another SBS. ORM releases us from the code translating into another DSB (not always).Judging by SqlConnection♪ SqlCommand You work exactly with Sql Server.What? https://docs.microsoft.com/en-us/sql/t-sql/statements/set-nocount-transact-sql?view=sql-server-ver15 ♪ If you need it, think for yourself.

We're sending a line from the server.response.send("succes"); I expect json on the client.const answer = await response.json(); The reason you made a mistake is to try a row steam using JSON.parse♪JSON.parse("succes")That's how they send json from the server.response.json("succes");

Yes, it's the introduction of any type into the numerical

The problem was socket.io. Stroke const socket = io.connect(url) inside the component. I put it to the component and the problem went away.

You need to write a relevant heading on your server. Here's the details of this: https://developer.mozilla.org/ru/docs/Web/HTTP/CORS/Errors/CORSMissingAllowOrigin

I found a mistake, pointed out an incorrect type in the interior, and I had to leave the type='text', and I wrote the type='search'

What's the button doing? That's right, sending the forms to the server. How? It's definitely not through the yacht. What should we do?Either. preventDefault() for the eventOr don't make a sabmit button, make a normal button, since the shape is formed through the axes anyway.form[1].addEventListener('click', onSubmit) async function onSubmit(e) { e.preventDefault(); ... }

The problem certainly can't be. CORS, as you've rightly noticed, the browsers are doing this test. From the website:The security model for XMLHtpRequest is different than on web as there is no concept of CORS in native apps.Maybe in the building. AndroidManifest.xml problem. Maybe you're trying. http I need to get to the server. https♪

If I'm not wrong, the body has to accept the object.body:{type:idType}

In js, you have to declare something like this. function fetchLoadPage(){ fetch('../php/loadPage.php', {/////////////////// отправка формы method: 'GET', }) .then(result =&gt; result.json()) .then((result) =&gt; { console.log(result) // json }) } On the server's side, check the headline. Content-Type: application/json@Alexey Ten in the commentaries made a reference, I'll note that the fetch documentation details the moment.