网站综合信息 www.samlam.com
    • 标题:
    • Sam Lam's Weblog | connecting dot 
    • 关键字:
    •  
    • 描述:
    • connecting dots . . . by looking backward -sj (by Sam) 
    • 域名信息
    • 域名年龄:27年4个月23天  注册日期:1998年09月12日  到期时间:2017年09月11日
      邮箱:registrar-abuse  电话:+1.8772376466
      注册商:GOOGLE INC. 
    • 备案信息
    • 备案号: 
    网站收录SEO数据
    • 搜索引擎
    • 收录量
    • 反向链接
    • 其他
    • 百度
    • 0  
    • 0  
    • 快照:无首页快照  
    • Google
    • 0  
    • 0  
    • pr:0  
    • 雅虎
    • 0  
    •  
    •  
    • 搜搜
    • 0  
    •  
    •  
    • 搜狗
    • 0  
    •  
    • 评级:1/10  
    • 360搜索
    • 1  
    •  
    •  
    域名流量Alexa排名
    •  
    • 一周平均
    • 一个月平均
    • 三个月平均
    • Alexa全球排名
    • -  
    • 平均日IP
    • 日总PV
    • 人均PV(PV/IP比例)
    • 反向链接
    • dmoz目录收录
    • -  
    • 流量走势图
    域名注册Whois信息

    samlam.com

    域名年龄: 27年4个月23天
    注册时间: 1998-09-12
    到期时间: 2017-09-11
    注 册 商: GOOGLE INC.
    注册邮箱: registrar-abuse
    联系电话: +1.8772376466

    获取时间: 2016年10月30日 09:23:29
    Domain Name: SAMLAM.COM
    Registrar: GOOGLE INC.
    Sponsoring Registrar IANA ID: 895
    Whois Server: whois.google.com
    Referral URL: http://domains.google.com
    Name Server: NS-CLOUD-C1.GOOGLEDOMAINS.COM
    Name Server: NS-CLOUD-C2.GOOGLEDOMAINS.COM
    Name Server: NS-CLOUD-C3.GOOGLEDOMAINS.COM
    Name Server: NS-CLOUD-C4.GOOGLEDOMAINS.COM
    Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
    Updated Date: 2016-08-08
    Creation Date: 1998-09-12
    Expiration Date: 2017-09-11

    >>> Last update of whois database: Sun, 2016-Oct-30 01:27:34 GMT <<<

    For more information on Whois status codes, please visit https://icann.org/epp

    Domain Name: samlam.com
    Registry Domain ID:
    Registrar WHOIS Server: whois.google.com
    Registrar URL: https://domains.google.com
    Updated Date: 2016-08-08T00:00:00Z
    Creation Date: 1998-09-12T00:00:00Z
    Registrar Registration Expiration Date: 2017-09-11T00:00:00Z
    Registrar: Google Inc.
    Registrar IANA ID: 895
    Registrar Abuse Contact Email: registrar-abuse
    Registrar Abuse Contact Phone: +1.8772376466
    Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
    Registry Registrant ID:
    Registrant Name: Contact Privacy Inc. Customer 124738270
    Registrant Organization: Contact Privacy Inc. Customer 124738270
    Registrant Street: 96 Mowat Ave
    Registrant City: Toronto
    Registrant State/Province: ON
    Registrant Postal Code: M4K 3K1
    Registrant Country: CA
    Registrant Phone: +1.4165385487
    Registrant Phone Ext:
    Registrant Fax:
    Registrant Fax Ext:
    Registrant Email: 1lmfft8cw5nl
    Registry Admin ID:
    Admin Name: Contact Privacy Inc. Customer 124738270
    Admin Organization: Contact Privacy Inc. Customer 124738270
    Admin Street: 96 Mowat Ave
    Admin City: Toronto
    Admin State/Province: ON
    Admin Postal Code: M4K 3K1
    Admin Country: CA
    Admin Phone: +1.4165385487
    Admin Phone Ext:
    Admin Fax:
    Admin Fax Ext:
    Admin Email: 1lmfft8cw5nl
    Registry Tech ID:
    Tech Name: Contact Privacy Inc. Customer 124738270
    Tech Organization: Contact Privacy Inc. Customer 124738270
    Tech Street: 96 Mowat Ave
    Tech City: Toronto
    Tech State/Province: ON
    Tech Postal Code: M4K 3K1
    Tech Country: CA
    Tech Phone: +1.4165385487
    Tech Phone Ext:
    Tech Fax:
    Tech Fax Ext:
    Tech Email: 1lmfft8cw5nl
    Name Server: NS-CLOUD-C1.GOOGLEDOMAINS.COM
    Name Server: NS-CLOUD-C2.GOOGLEDOMAINS.COM
    Name Server: NS-CLOUD-C3.GOOGLEDOMAINS.COM
    Name Server: NS-CLOUD-C4.GOOGLEDOMAINS.COM
    DNSSEC: unsigned
    URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
    >>> Last update of WHOIS database: 2016-10-30T01:26:54Z <<<

    For more information on Whois status codes, please visit
    https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en

    Please register your domains at: https://domains.google.com/
    This data is provided by Google for information purposes, and to assist
    persons obtaining information about or related to domain name registration
    records. Google does not guarantee its accuracy.
    By submitting a WHOIS query, you agree that you will use this data only for
    lawful purposes and that, under no circumstances, will you use this data to:
    1) allow, enable, or otherwise support the transmission of mass
    unsolicited, commercial advertising or solicitations via E-mail (spam); or
    2) enable high volume, automated, electronic processes that apply to this
    WHOIS server.
    These terms may be changed without prior notice.
    By submitting this query, you agree to abide by this policy.
    其他后缀域名
    • 顶级域名
    • 相关信息
    网站首页快照(纯文字版)
    抓取时间:2013年12月15日 17:22:41
    网址:http://www.samlam.com/
    标题:Sam Lam's Weblog | connecting dots . . . by looking bac
    关键字:
    描述:connecting dots . . . by looking backward -sj (by Sam)
    主体:
    Sam Lam's WeblogMain menuSkip to contentHomeconnecting dots . . . by looking backward  -sjPost navigation← Older postsCheck IE VersionPosted on September 26, 2013  by  Sam0Check IE VersionIE Browser detection (best solution)Posted in Javascript, ProgrammingTagged JavascriptIE 8/9 CORS support in Angular.jsPosted on August 3, 2013  by  Sam10Many would agree with me that to create a website to run on IE is a headache chore. I would have dropped the IE browser if we were given that choice. Our team has decided to use Angular as our primary html platform. It works great and we all loved it, until the app started to break in IE, which is caused by  lack of IE cors (cross-origin-resource-sharing) support. Angular had a solution to use XDomainRequest, but removed due to its limited capabilities. Fortunately, there’s a better solution. Let’s go over the steps:First, we have to hijack the $http service. So that it can support IE CORS when detected. On the main application where Angular is expected to access the resources (templates/API) on another server, we will modify the angular.js file to use our very own httpBackendProvider. Find the $HttpBackendProvider function and replace it as below (roughly between 9200 to 9300 line, for v1.0.7)function $HttpBackendProvider() {this.$get = ['$browser', '$window', '$document', function($browser, $window, $document) {var params = [$browser, XHR, $browser.defer, $window.angular.callbacks, $document[0], $window.location.protocol.replace(':', '')]; /*orig xhr */var param4ie = params.concat([msie,createHttpBackend.apply(this,params)]);return (angular.ieCreateHttpBackend && angular.ieCreateHttpBackend.apply(this, param4ie)) ||createHttpBackend.apply(this, params);}];}2nd step is to create the ieCreateHttpBackend method and that’s where we put the override logic for IE CORS support. see the code below, we are extending angular namespace with the new function ieCreateHttpBackend. Lets save it as angular.ieCors.js, be sure to wrap it as a self invoking function. window.angular = {ieCreateHttpBackend: function ($browser, XHR, $browserDefer, callbacks, rawDocument, locationProtocol, msie, xhr) {if (!msie || msie > 9) return null;var getHostName = function (path) {var a = document.createElement('a');a.href = path;return a.hostname;}var isLocalCall = function (reqUrl) {var reqHost = getHostName(reqUrl),localHost = getHostName($browser.url());patt = new RegExp( localHost + "$", 'i'); return patt.test(reqHost);}function completeRequest(callback, status, response, headersString) {var url = url || $browser.url(),URL_MATCH = /^([^:]+):\/\/(\w+:{0,1}\w*@)?(\{?[\w\.-]*\}?)(:([0-9]+))?(\/[^\?#]*)?(\?([^#]*))?(#(.*))?$/;// URL_MATCH is defined in src/service/location.jsvar protocol = (url.match(URL_MATCH) || ['', locationProtocol])[1];// fix status code for file protocol (it's always 0)status = (protocol == 'file') ? (response ? 200 : 404) : status;// normalize IE bug (http://bugs.jquery

    © 2010 - 2020 网站综合信息查询 同IP网站查询 相关类似网站查询 网站备案查询网站地图 最新查询 最近更新 优秀网站 热门网站 全部网站 同IP查询 备案查询

    2026-01-26 06:13, Process in 0.0125 second.