Bas ten Berge

I tried to work this out and found that the block names are present in `context.render_context[BLOCK_CONTEXT_KEY]`. That got me thinking. PR coming up

Looks like I'm introducing a new issue here. I'll look into that ``` ... File "/var/www/brownpapersession/dev/env-brownpapersession/local/lib/python2.7/site-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/var/www/brownpapersession/dev/env-brownpapersession/local/lib/python2.7/site-packages/django/template/base.py", line 960, in render_annotated e.template_debug...

Maybe also consider caching the content in a caching engine, like memcached. Or redis. Or elasticsearch? Better yet: what about making the entire caching engine user extendable and ship it...

I noticed the same behaviour a couple of weeks ago. My setup was `python manage.py runserver` behind nginx for SSL offloading. It did not appear to happen when the websocket...

Reproducer for the double wsa headers for python 3: ``` from lxml import etree from requests import Session from zeep import Client, Settings from zeep.transports import Transport from zeep.wsa import...

It gets a bit more confusing when you attempt to override via `_soapheaders` *and* use the `plugins`. You'll end up with additional headers found in `_soapheaders`.

@renevdkooi I'm able to connect to the preprod environment and retrieve data, but not using zeep. Happy to discuss how I did it.

Sure, contact me via [email protected]. It'll take me some time to respond though.

@zeyadmbk just letting you know I didn't use PHP, so I'm afraid I can't help with PHP code. I used the `requests` module to send the message because I was...