diff options
author | corvid <devnull@localhost> | 2015-06-03 07:54:16 +0000 |
---|---|---|
committer | corvid <devnull@localhost> | 2015-06-03 07:54:16 +0000 |
commit | 59b76c75b64578edac35d19c914067a0bd7791e9 (patch) | |
tree | 00e8d89d471680b2c4f20e9579165b79c91479db /devdoc/dw-overview.doc | |
parent | d15ff594d989c0fdd025b9f66da8d83ff4dd2629 (diff) |
web must be valid in order to continue in a_Http_connect_done
A site triggers this with a background image where the style is deleted
upon </div>, and Capi_stop_client() finds that a_Cache_client_get_if_unique()
is false, so nothing aborts the connection. And there's time for this to
happen because we're doing TLS handshake.
I don't know whether all of what triggered this is doing the right thing,
but at least when it comes to capi, we can see that there's the idea of
permitting it (with whether we ever actually want that in practice being
yet another question).
In any case, Http_make_query_str() definitely thinks the web is there.
If we really decided that we wanted connections to continue without webs,
we could stuff 1) what sort of thing are we requesting? 2) is this a
third-party request? into the socket data. Making the query earlier is
probably not advisable because we'd want the cookies available at the
time that we send the query and not the cookies that were available
somewhat earlier.
Diffstat (limited to 'devdoc/dw-overview.doc')
0 files changed, 0 insertions, 0 deletions