
GITHUB . COM {
}
Detected CMS Systems:
- Wordpress (2 occurrences)
Title:
Drop the json-to-jsonp auto-promoting logic Β· Issue #3376 Β· jquery/jquery
Description:
Description Currently jQuery.ajax with dataType: 'json' gets automatically converted to a jsonp request unless one also specifies jsonp: false. Today the preferred way of interacting with a...
Website Age:
17 years and 8 months (reg. 2007-10-09).
Matching Content Categories {π}
- Mobile Technology & AI
- Technology & Computing
- Video & Online Content
Content Management System {π}
What CMS is github.com built with?
Github.com uses WORDPRESS.
Traffic Estimate {π}
What is the average monthly size of github.com audience?
ππ Tremendous Traffic: 10M - 20M visitors per month
Based on our best estimate, this website will receive around 10,000,019 visitors per month in the current month.
However, some sources were not loaded, we suggest to reload the page to get complete results.
check SE Ranking
check Ahrefs
check Similarweb
check Ubersuggest
check Semrush
How Does Github.com Make Money? {πΈ}
Subscription Packages {π³}
We've located a dedicated page on github.com that might include details about subscription plans or recurring payments. We identified it based on the word pricing in one of its internal links. Below, you'll find additional estimates for its monthly recurring revenues.How Much Does Github.com Make? {π°}
Subscription Packages {π³}
Prices on github.com are in US Dollars ($).
They range from $4.00/month to $21.00/month.
We estimate that the site has approximately 4,989,889 paying customers.
The estimated monthly recurring revenue (MRR) is $20,957,532.
The estimated annual recurring revenues (ARR) are $251,490,385.
Wordpress Themes and Plugins {π¨}
What WordPress theme does this site use?
It is strange but we were not able to detect any theme on the page.
What WordPress plugins does this website use?
It is strange but we were not able to detect any plugins on the page.
Keywords {π}
jsonp, mgol, ajax, json, drop, logic, issue, added, autopromotion, sign, requests, jsontojsonp, false, mentioned, jquery, code, security, autopromoting, datatype, timmywil, krinkle, commented, member, navigation, pull, actions, description, request, browsers, behavior, change, milestone, ive, promotion, supportcors, commits, reference, github, type, projects, footer, skip, content, menu, product, solutions, resources, open, source, enterprise,
Topics {βοΈ}
jsonp auto-promotion logic auto-promoting json requests krinkle edits member 41c9cf4 mgol mentioned b1bece3 mgol mentioned mgol added security issue org/rest/foo' requiring additional options comment metadata assignees due date relationships personal information drop cross-domain backend require requests jsonp promotion executing code adding code promotion behaviour jsonp request type projects specifies jsonp true jsonp set jsonp setting jsonp jquery b29bbd0 ajax 5f93f8e ajax [wip] drop projects milestone 4 automatically converted long time downloading data remote domain explicit pattern question mark modern browsers github automatic json jsonp 'jsonp' } ajax drop cors+json browsers //remote json 'json' json cors skip
Payment Methods {π}
- Braintree
Questions {β}
- Already have an account?
- Will this continue to use CORS+JSON for modern browsers, using JSONP as fallback only - without requiring additional options to be passed?
- Cors ?
Schema {πΊοΈ}
DiscussionForumPosting:
context:https://schema.org
headline:Drop the json-to-jsonp auto-promoting logic
articleBody:<!--
Feature Requests:
Please read https://github.com/jquery/jquery/wiki/Adding-new-features
Most features should start as plugins outside of jQuery.
Bug Reports:
Note that we only can fix bugs in the latest (1.x, 2.x, 3.x) versions of jQuery.
Briefly describe the issue you've encountered
* What do you expect to happen?
* What acually happens?
* Which browsers are affected?
Provide a *minimal* test case, see https://webkit.org/test-case-reduction/
Use the latest shipping version of jQuery in your test case!
We prefer test cases on https://jsbin.com or https://jsfiddle.net
Frequently Reported Issues:
* Selectors with '#' break: See https://github.com/jquery/jquery/issues/2824
-->
### Description
Currently jQuery.ajax with `dataType: 'json'` gets automatically converted to a jsonp request unless one also specifies `jsonp: false`. Today the preferred way of interacting with a cross-domain backend is CORS which has been supported by browsers for a long time (the only roadblock is if someone requires IE 9 support).
Auto-promoting JSON requests to JSONP ones introduces a security issue as the developer may be unaware they're not just downloading data but executing code from a remote domain.
The first step in the migration could be adding code to Migrate that would require requests with `dataType: 'json'` to always specify ~~`jsonp: true`~~ `jsonp: callbackName` or `jsonp: false`.
### Link to test case
author:
url:https://github.com/mgol
type:Person
name:mgol
datePublished:2016-10-24T16:56:24.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:3
url:https://github.com/3376/jquery/issues/3376
context:https://schema.org
headline:Drop the json-to-jsonp auto-promoting logic
articleBody:<!--
Feature Requests:
Please read https://github.com/jquery/jquery/wiki/Adding-new-features
Most features should start as plugins outside of jQuery.
Bug Reports:
Note that we only can fix bugs in the latest (1.x, 2.x, 3.x) versions of jQuery.
Briefly describe the issue you've encountered
* What do you expect to happen?
* What acually happens?
* Which browsers are affected?
Provide a *minimal* test case, see https://webkit.org/test-case-reduction/
Use the latest shipping version of jQuery in your test case!
We prefer test cases on https://jsbin.com or https://jsfiddle.net
Frequently Reported Issues:
* Selectors with '#' break: See https://github.com/jquery/jquery/issues/2824
-->
### Description
Currently jQuery.ajax with `dataType: 'json'` gets automatically converted to a jsonp request unless one also specifies `jsonp: false`. Today the preferred way of interacting with a cross-domain backend is CORS which has been supported by browsers for a long time (the only roadblock is if someone requires IE 9 support).
Auto-promoting JSON requests to JSONP ones introduces a security issue as the developer may be unaware they're not just downloading data but executing code from a remote domain.
The first step in the migration could be adding code to Migrate that would require requests with `dataType: 'json'` to always specify ~~`jsonp: true`~~ `jsonp: callbackName` or `jsonp: false`.
### Link to test case
author:
url:https://github.com/mgol
type:Person
name:mgol
datePublished:2016-10-24T16:56:24.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:3
url:https://github.com/3376/jquery/issues/3376
Person:
url:https://github.com/mgol
name:mgol
url:https://github.com/mgol
name:mgol
InteractionCounter:
interactionType:https://schema.org/CommentAction
userInteractionCount:3
interactionType:https://schema.org/CommentAction
userInteractionCount:3
External Links {π}(2)
Analytics and Tracking {π}
- Site Verification - Google
Libraries {π}
- Clipboard.js
- D3.js
- jQuery
- Lodash
Emails and Hosting {βοΈ}
Mail Servers:
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
Name Servers:
- dns1.p08.nsone.net
- dns2.p08.nsone.net
- dns3.p08.nsone.net
- dns4.p08.nsone.net
- ns-1283.awsdns-32.org
- ns-1707.awsdns-21.co.uk
- ns-421.awsdns-52.com
- ns-520.awsdns-01.net