Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The current state of standardizing the <a href="http://www.w3.org/TR/XMLHttpRequest/" rel="noreferrer">XMLHttpRequest API</a> does only restrict the access to the <em>Set-Cookie</em> and <em>Set-Cookie2</em> header fields:</p> <blockquote> <p><strong><em>client</em>.getAllResponseHeaders()</strong></p> <p>Returns all headers from the response, with the exception of those whose field name is <code>Set-Cookie</code> or <code>Set-Cookie2</code>.</p> </blockquote> <p>Any other header field should be returned.</p> <p>But as you’re doing a cross-origin request, the browser needs to implement <a href="http://www.w3.org/TR/XMLHttpRequest2/" rel="noreferrer">XMLHttpRequest Level 2</a> as the original XMLHttpRequest does only allow same-origin requests:</p> <blockquote> <p>The XMLHttpRequest Level 2 specification enhances the XMLHttpRequest object with new features, such as cross-origin requests […]</p> </blockquote> <p>There you can read that the “<a href="http://www.w3.org/TR/cors/" rel="noreferrer">Cross-Origin Resource Sharing specification</a> filters the headers that filters the headers that are exposed by <a href="http://www.w3.org/TR/XMLHttpRequest2/#the-getallresponseheaders-method" rel="noreferrer">getResponseHeader()</a> for non <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/origin-0.html#same-origin" rel="noreferrer">same-origin</a> requests.”. And that specification forbids access to any response header field other except the <a href="http://www.w3.org/TR/cors/#simple-response-header" rel="noreferrer">simple response header fields</a> (i.e. <em>Cache-Control</em>, <em>Content-Language</em>, <em>Content-Type</em>, <em>Expires</em>, <em>Last-Modified</em>, and <em>Pragma</em>):</p> <blockquote> <p>User agents must filter out all response headers other than those that are a simple response header […]</p> <p>E.g. the <code>getResponseHeader()</code> method of XMLHttpRequest will therefore not expose any header not indicated above.</p> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. PORestrictions of XMLHttpRequest's getResponseHeader()?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USGumbo
    1. USGumbo
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORestrictions of XMLHttpRequest's getResponseHeader()?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CORight, thanks. There are still some mysteries left, though.. I've set a proper `Access-Control-Expose-Headers:` -- only to find out it works only in Gecko, not WebKit. WebKit happily "Refused to get unsafe header (..)", Gecko sees no problem. Second issue: `getAllResponseHeaders()` lies. I can `getResponseHeader()` headers that the former doesn't list as available.
      singulars
      1. PO
      1. USmaligree
    2. CO@maligree: [WebKit doesn’t support the *Access-Control-Expose-Headers* yet.](https://bugs.webkit.org/show_bug.cgi?id=41210) But what about the other issue? What browser does that?
      singulars
      1. PO
      1. USGumbo
    3. COYes, I've stumbled upon that bugzilla issue -- but seeing the date it was opened, I took it with a grain of salt . *And* as to the second issue, I'm seeing this in Firefox 6. `getAllResponseHeaders()` returns `""`, while a `getResponseHeader('content-length')` or `getResponseHeader('www-authenticate')` (which is one of the headers I'm setting and `Access-Control-Expose-Header`'ing) returns the proper header value. I'd rather not expose the URI used at this time, but if it helps, I can devise an isolated test case later.
      singulars
      1. PO
      1. USmaligree
 

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