Have you inspected your HTTP traffic, specifically the POST request
that your client sends? Your client might be sending the image/x-png
as a Content-Type header. Not 100% sure that the SlingPostServlet
takes that into account, but I think it does.
Regards
Julian
On Fri, Oct 9, 2015 at 9:38 PM,
I've been *trying* to do that, but I have not succeeded in getting my proxy to
intercept those calls. I'll focus some more effort on that.
-Original Message-
From: Julian Sedding [mailto:jsedd...@gmail.com]
Sent: Friday, October 09, 2015 5:01 PM
To: users@sling.apache.org
Subject: Re:
I was able to configure the proxy and I discovered that you are right, Julian.
The request looks like this:
Content-Disposition: form-data; name="file";
filename="01-4970B5C0-8905-426E-B644-9D809833CDE5.png"
Content-Type: image/x-png
Content-Length: 852326
So now I need to figure out where
So if I understand correctly there are two possibilities:
1. A bundle was added at some point which changed the MIME mappings for PNG. Am
I correct in assuming that any change would be reflected in the MIME registry
as viewed from the Web Console? The mapping looks correct in my current
Simply adding that bundle to my app doesn't seem to do the trick. Also, it
looks like this discussion was centered on the Simple WebDav Servlet, however I
am using the POST Servlet in my case. Is there a way to configure the POST
servlet to use the content detection? My use case is low-volume
On Fri, Oct 9, 2015 at 9:02 PM, Roll, Kevin wrote:
> Simply adding that bundle to my app doesn't seem to do the trick. Also, it
> looks like this discussion was centered on the Simple WebDav Servlet, however
> I am using the POST Servlet in my case. Is there a way to
And I thought you were recommending that bundle as a solution. :) I'm still
completely stumped here. The MIME mapping table looks fine in the Web Console,
and I can't see any vast difference in the way these POSTs are done. Yet, I get
the type "image/x-png", whereas a few months ago it properly
On Fri, 2015-10-09 at 13:17 +, Roll, Kevin wrote:
> So if I understand correctly there are two possibilities:
>
> 1. A bundle was added at some point which changed the MIME mappings
> for PNG. Am I correct in assuming that any change would be reflected
> in the MIME registry as viewed from