Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
branch: master
Commits on Jun 6, 2014
  1. Update LICENSE.md

    authored
Commits on Jan 6, 2014
  1. Update README.md

    authored
  2. Update README.md

    authored
  3. No longer considering pmxdr.originRegex public

    authored
    Misconfiguring pmxdr.originRegex can reduce security, so it's best to keep it as is.
  4. Update readme for #12

    authored
  5. Merge pull request #12 from Baboom/master

    authored
    Ability to specify endpoint mappings.
Commits on Dec 29, 2013
  1. @satazor

    Ability to specify endpoint mappings.

    satazor authored
    Also fix a bug with safe id.
Commits on Jul 3, 2013
  1. Closes #9

    authored
  2. Closes #10

    authored
Commits on Jul 2, 2013
  1. Update README.md

    authored
Commits on Jun 24, 2013
  1. Merge pull request #8 from fidian/fix-ie-1223

    authored
    Handle Internet Explorer's status=1223 quirk + restructuring
  2. @fidian

    Turn the warning back on

    fidian authored
  3. @fidian

    Restructruing code and supporting IE's 1223 status

    fidian authored
    Restructuring code so it is broken out into commented functions.
    
    Handle a wider variety of errors.
    
    IE may report status 1223 with a 204 No Content response.  At that point, one
    can not get any of the headers.  Instead of getting CORS failures, this will
    use the headers from a previous OPTIONS call.
    
    * Do an OPTIONS call before the real call so we can get headers that may be
    applicable to the response in the case that the response is a 204.
    
    * If we get status code 1223, override the code and message to be reasonable.
    Override the CORS-related headers to be the OPTIONS call's response.
    
    * Must check the OPTIONS before we do any API manipulation in case we are
    changing the information on the server.  It is possible that we are allowed
    to POST once to a resource and it takes an action.  A subsequent OPTIONS call
    might rightly say that you can not POST to that resource again, thus we must
    not call OPTIONS after our POST.
  4. @fidian

    Using alternate JSON.stringify/JSON.parse

    fidian authored
    Instead of using packer, using straight minified code as a big string.
    Instead of using the `eval` version, using a minifed `JSON.parse` method instead.
    Added comments and using eval to get through JSLint.
    
    End result is approximately the same and there's just one potential warning for
    using eval instead of many coding violations.  If you use other validation
    tools, like jshint, this one line eval would be easier to ignore.
  5. @fidian
Commits on Apr 15, 2013
  1. Merge pull request #7 from fidian/master

    authored
    I had the logic backwards with checking this.status
Commits on Apr 12, 2013
  1. @fidian

    I had the logic backwards.

    fidian authored
    If the status is truthy (ie. 200, 201, 400, 500, etc), then we want everything possible.  If the status is falsy (undefined, 0, empty string), then something is severely wrong and we can't assume anything is really there or anything is really correct.
Commits on Apr 8, 2013
  1. Merge pull request #6 from fidian/master

    authored
    Fixing caching header to be maximum date allowed on XP
  2. @fidian

    Changing the date so IE caches the page

    fidian authored
    It turns out that IE8 on Windows XP (a 32-bit operating system) internally must store dates in the same way that MS-DOS file timestamps are stored.  It uses 16 bits for a date and 16 bits for a time, and it starts the clock at 1980-01-01 00:00:00 (no time zone information) and ends at 2107-12-31 23:59:58.  The seconds may seem odd, but MS-DOS drops the resolution of the seconds down to just even numbers in order to squeeze it into 16 bits.
    
    Here's a bitwise breakdown for more information:
    
        FEDC BA98 7654 3210   FEDC BA98 7654 3210
        YYYY YYYM MMMD DDDD   HHHH Hmmm mmmS SSSS
    
    You will get the possible maximums as:
        Y (year): 127
    	M (month): 16
    	D (day): 31
    	H (hour): 31
    	m (minute): 63
    	S (seconds / 2): 31
    
    So, because S can only go up to 31, only even numbers of seconds are stored, giving you a granularity down to a 2 second margin.
Commits on Apr 4, 2013
  1. Merge pull request #5 from fidian/load-error

    authored
    Allow capturing of non-200 responses
  2. @fidian
  3. @fidian

    Allow other HTTP status codes to be sent to client

    fidian authored
    When dealing with RESTful services, we won't always get 200 replies.  It can
    be normal to receive and handle any HTTP status code.  I was using 500, 409
    and 202 today.
Commits on Apr 3, 2013
  1. Fixed tracking image

    authored
  2. Cleaned up readme

    authored
  3. Merge pull request #4 from fidian/apache

    authored
    Adding examples from official website
  4. @fidian

    Adding examples from official website

    fidian authored
    It's handy to have everything you need in one repository.
    Source files were mostly pulled from Eli's website with only a minor edit.
    http://eligrey.com/blog/post/pmxdr-postmessage-cross-domain-request-library
  5. Merge pull request #3 from fidian/master

    authored
    Comma fix for IE8 with pmxdr-host.js
  6. @fidian

    Removing comma for IE8

    fidian authored
Commits on Mar 11, 2013
  1. Merge pull request #2 from fidian/master

    authored
    Removing extra comma
  2. @fidian

    Removing extra comma

    fidian authored
    This causes failure when in IE8 rendering as IE7.
Commits on May 12, 2011
Commits on Oct 12, 2010
  1. Updated license to MIT-only.

    authored
Commits on Sep 21, 2010
  1. Added @source comments.

    authored
Commits on May 28, 2010
Commits on May 11, 2010
Something went wrong with that request. Please try again.