Databases
StackOverflow2013
Postsdbo
POHow to get a cross-origin resource sharing (CORS) post request working
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to get a cross-origin resource sharing (CORS) post request working
    primarykey
    data
    text
    <p>I have a machine on my local lan (machineA) that has two web servers. The first is the in-built one in XBMC (on port 8080) and displays our library. The second server is a CherryPy python script (port 8081) that I am using to trigger a file conversion on demand. The file conversion is triggered by a AJAX POST request from the page served from the XBMC server.</p> <ul> <li>Goto <a href="http://machineA:8080" rel="noreferrer">http://machineA:8080</a> which displays library</li> <li>Library is displayed</li> <li>User clicks on 'convert' link which issues the following command - </li> </ul> <p>jQuery Ajax Request</p> <pre><code>$.post('http://machineA:8081', {file_url: 'asfd'}, function(d){console.log(d)}) </code></pre> <ul> <li>The browser issues a HTTP OPTIONS request with the following headers;</li> </ul> <p><strong>Request Header - OPTIONS</strong></p> <pre><code>Host: machineA:8081 User-Agent: ... Firefox/4.01 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Connection: keep-alive Origin: http://machineA:8080 Access-Control-Request-Method: POST Access-Control-Request-Headers: x-requested-with </code></pre> <ul> <li>The server responds with the following;</li> </ul> <p><strong>Response Header - OPTIONS (STATUS = 200 OK)</strong></p> <pre><code>Content-Length: 0 Access-Control-Allow-Headers: * Access-Control-Max-Age: 1728000 Server: CherryPy/3.2.0 Date: Thu, 21 Apr 2011 22:40:29 GMT Access-Control-Allow-Origin: * Access-Control-Allow-Methods: POST, GET, OPTIONS Content-Type: text/html;charset=ISO-8859-1 </code></pre> <ul> <li>The conversation then stops. The browser, should in theory, issue a POST request as the server responded with the correct (?) CORS headers (Access-Control-Allow-Origin: *)</li> </ul> <p>For troubleshooting, I have also issued the same $.post command from <a href="http://jquery.com" rel="noreferrer">http://jquery.com</a>. This is where I am stumped, from jquery.com, the post request works, a OPTIONS request is sent following by a POST. The headers from this transaction are below;</p> <p><strong>Request Header - OPTIONS</strong></p> <pre><code>Host: machineA:8081 User-Agent: ... Firefox/4.01 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Connection: keep-alive Origin: http://jquery.com Access-Control-Request-Method: POST </code></pre> <p><strong>Response Header - OPTIONS (STATUS = 200 OK)</strong></p> <pre><code>Content-Length: 0 Access-Control-Allow-Headers: * Access-Control-Max-Age: 1728000 Server: CherryPy/3.2.0 Date: Thu, 21 Apr 2011 22:37:59 GMT Access-Control-Allow-Origin: * Access-Control-Allow-Methods: POST, GET, OPTIONS Content-Type: text/html;charset=ISO-8859-1 </code></pre> <p><strong>Request Header - POST</strong></p> <pre><code>Host: machineA:8081 User-Agent: ... Firefox/4.01 Accept: */* Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Connection: keep-alive Content-Type: application/x-www-form-urlencoded; charset=UTF-8 Referer: http://jquery.com/ Content-Length: 12 Origin: http://jquery.com Pragma: no-cache Cache-Control: no-cache </code></pre> <p><strong>Response Header - POST (STATUS = 200 OK)</strong></p> <pre><code>Content-Length: 32 Access-Control-Allow-Headers: * Access-Control-Max-Age: 1728000 Server: CherryPy/3.2.0 Date: Thu, 21 Apr 2011 22:37:59 GMT Access-Control-Allow-Origin: * Access-Control-Allow-Methods: POST, GET, OPTIONS Content-Type: application/json </code></pre> <p>I can't work out why the same request would work from one site, but not the other. I am hoping someone might be able to point out what I am missing. Thanks for your help!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJames
    1. USJames
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to get a cross-origin resource sharing (CORS) post request working
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow to get a cross-origin resource sharing (CORS) post request working
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow to get a cross-origin resource sharing (CORS) post request working
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIs CORS needed if both web servers are on the same machine?
      singulars
      1. POHow to get a cross-origin resource sharing (CORS) post request working
      1. USjdigital
    2. COTo the best of my knowledge it is a CORS request because of the different port. Also, the OPTIONS request indicates that the browser is treating it as a CORS request
      singulars
      1. POHow to get a cross-origin resource sharing (CORS) post request working
      1. USJames
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload