OK, sounds good. 2009 plus a few years for browsers I use to catch up
sounds about the right timing to me.
-Alex
On 2/28/17, 2:21 PM, "Greg Dove" wrote:
>Thanks Alex,
>
>At this point I assume that removing these headers does not relate to
>'Trusted'/ 'Untrusted', so I will remove them as it a
Thanks Alex,
At this point I assume that removing these headers does not relate to
'Trusted'/ 'Untrusted', so I will remove them as it appears to me to be
currently broken.
These are currently not permitted [1]
As near as I can tell it has been not permitted since at least 2009 specs
[2]
I may be
Oh yeah, forgot about that.
I thought this code worked at one point, maybe four or five years ago, but
I was unable to find out when browsers started blocking it, so we can
truly understand if it will never be needed again or will be needed on
some older browser.
It could be the right answer is t
Justin logged a bug here and I encountered the same issue:
https://issues.apache.org/jira/browse/FLEX-35271
At first glance this seems like a real quick fix, just delete the two lines
from :
if (contentData) {
element.setRequestHeader('Content-length', contentData.length.toString());
e
