> It looks like when connected to some HTTPS servers, the TLS
connection is not successfully closed.
> But with Office365 sharepoint.com sites the TLS shutdown is not completed.
> Has anyone else observed this behaviour ?
I observed something simillar a while ago, there was bug report created for
> Anyway, I’ll be spending my Twisted time on this for a while I suspect.
This will delay HTTP/2 client support, unfortunately. =(
Isn't it better to get HTTP2 client support and just document things better
for HTTP2? Or maybe even backport some features from CertificateOptions to
factory? Default
it
does not look that difficult. If you think about this, you probably dont
need to check ciphers available in system, you can probably only
check OpenSSL version available and check if client attempts to use ALPN.
2016-07-12 17:13 GMT+02:00 Cory Benfield :
>
> On 12 Jul 2016, at 09:33, Pawe
> DefaultOpenSSLContextFactory should have been deprecated a long time ago.
It’s insecure, and in particular does not set a cipher string, so it uses
DEFAULT. That will have all kinds of messed up priorities. For that reason,
you should adjust your code to use OpenSSLCertificateOptions or, even
bet
> In an earlier e-mail you mentioned that you were using Python 3. Is that
still true?
I can reproduce this in Python 2.7.11 and Python 3.5.2. In both of them
Chrome responds with ERR_SPDY_INADEQUATE_TRANSPORT_SECURITY. When I test
with curl with verbose flag I see that it also shows information
ec/#BadCipherSuites
2016-07-11 21:22 GMT+02:00 Glyph Lefkowitz :
>
> On Jul 11, 2016, at 3:35 AM, Cory Benfield wrote:
>
>
> On 11 Jul 2016, at 01:45, Glyph Lefkowitz wrote:
>
>
> On Jul 9, 2016, at 10:30 AM, Paweł Miech wrote:
>
> My question is: should user deal with
Craig Rodrigues :
> On Sun, Jul 3, 2016 at 3:15 AM, Paweł Miech wrote:
>
>> HTTP2 support sounds really exciting.
>>
>> > Please let me know if you have any issues, as well as if you don't! If
>> everything works well, that's a good thing for me to know :
but the error is raised when I send it as a whole, when I
only send some smaller chunk (e.g. first 100 items from file) it seems to
work ok. It seems that Python-hyper is all right with this file, perhaps
curl --http2 does something weird.
2016-07-03 12:50 GMT+02:00 Adi Roiban :
>
>
&
HTTP2 support sounds really exciting.
> Please let me know if you have any issues, as well as if you don't! If
everything works well, that's a good thing for me to know :)
I played around with this today and found out that the command you
recommend:
> pip install -U https://twistedmatrix.com/Re
seemed fresh and updated. I remember some
discussion on mailing list about moving issue tracking to github, is
today's migration part of this process? Are there plans to accept pull
requests on github?
Paweł Miech
2016-05-10 18:29 GMT+02:00 Amber "Hawkie" Brown :
> Hi everyone
I get following message:
> Submission rejected as potential spam
> SpamBayes determined spam probability of 74.83
SpamBayes seems to hate new users...
This is after trying to submit following bug report:
Executive summary page(
http://twistedmatrix.com/documents/current/core/howto/vision.html)
Hello,
I submitted some patches yesterday, got review from Adi and today I tried
to respond. However I'm not able to respond because all my submissions are
marked as spam and blocked by SpamBayes with super high probability. I
wonder how many other users experience that problem?
Can you please fi
12 matches
Mail list logo
