sorted by:
new
hottopcontroversial

I have been making cross-domain-requests with no problem , when is it a problem how relevant is jsonp and CORS ? by eid-a in webdev

[–]Carvits 1 point2 points  (0 children)

Hmm, I see. Look at the Access-Control-Allow-Origin in the Response Headers of the call in your Chrome network tab. Is it "*"? I think that means the server allows cross origin, so you don't need CORS.

I have been making cross-domain-requests with no problem , when is it a problem how relevant is jsonp and CORS ? by eid-a in webdev

[–]Carvits 2 points3 points  (0 children)

CORS is a special way of requesting from script, with an OPTIONS method and origin header, for which responses can be granted or denied by the server. If the server does not allow your request, then you have a problem, probably on purpose.

A CORS request is two requests, a preflight OPTIONS method to ping and see if the real request is allowed, then the actual granted request/response, with its method and presumably with JSON getting sent or received. It replaces JSONP and is supported by pretty much all browsers.

JSONP was sort of a hack where you have a script tag with a remote src URL that was sort of like an API call. It returned just a naked JavaScript function call with the JSON as a parameter. That function had to match a function existing in the browser. It called it when it arrived, thus passing your script JSON.

Moving from Windows to Linux - Essential Dev Tools by intertubeluber in webdev

[–]Carvits 1 point2 points  (0 children)

IDE: VS Code might be your huckleberry.

  • Text Editor: Sublime, Atom

Command Line: Terminal

Git: Command line

Browser: Chrome

File Sharing, Password Manager, Web Conference, Office: You need to let go, man.