By Ken on Thursday, 30 October 2014
Posted in General Issues
Likes 0
Views 0.9K
Votes 0
Hi there, just want to ask why am I always having http error while uploading images on MOBILE after I upgrade.
Hi Ken,

I believe this is similar to the issue that you've posted: http://stackideas.com/forums/upload-stopped-after-adding-cdn-and-amazon
·
Wednesday, 12 November 2014 10:51
·
0 Likes
·
0 Votes
·
0 Comments
·
Sorry I forgot to add attachments
Ken
·
Thursday, 30 October 2014 11:39
·
0 Likes
·
0 Votes
·
0 Comments
·
hello Ken ,

Sorry for late reply to this,
I have tried to upload the image from mobile, it seems like work fine for me. Check my screenshot below.
May i know which phone model are you using? Please advise.
·
Thursday, 30 October 2014 12:30
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Ken, I wonder if yours is similar to my error I got here: http://stackideas.com/forums/photo-upload-fails-sometimes

Have you been able to find the cause of this by any chance?
·
Wednesday, 12 November 2014 04:29
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Jason, thanks for the update! I managed to change the header. basically I'm testing all the security flaws on my server. Sorry for consuming your time over my fault. kudos to your team too!
Ken
·
Wednesday, 12 November 2014 17:09
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi,

After changing the header, is the upload ok now?
·
Wednesday, 12 November 2014 17:15
·
0 Likes
·
0 Votes
·
0 Comments
·
As for the profile upload, yes. As for the upgrade, I haven't upgraded yet but I believe it will solve the issue too

Thanks a lot Jason!
Ken
·
Wednesday, 12 November 2014 17:24
·
0 Likes
·
0 Votes
·
0 Comments
·
When you say header, do you mean the header timeout? Can you elaborate on the fix a little bit plz so we can understand what worked in your case?
·
Wednesday, 12 November 2014 17:24
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi there Neel, due to some security risk, I added this on my nginx.conf

more_clear_headers "Content-Type: ";
more_clear_headers "Accept-Ranges: ";
more_clear_headers "Content-Length: ";

That causes the error on my side. I just deleted it and restart nginx and everything works as expected. Basically, Jason gives me the hint (top class @Jason)
Ken
·
Wednesday, 12 November 2014 17:27
·
0 Likes
·
0 Votes
·
0 Comments
·
@Ken great! You're most welcome.

@Neel refer to my reply here: http://stackideas.com/forums/upload-stopped-after-adding-cdn-and-amazon

It is mainly caused by the fact that, nginx didn't return a proper ContentType header. I am not sure though if this applies to your case.
·
Wednesday, 12 November 2014 17:28
·
0 Likes
·
0 Votes
·
0 Comments
·
Ken wrote:

Hi there Neel, due to some security risk, I added this on my nginx.conf

more_clear_headers "Content-Type: ";
more_clear_headers "Accept-Ranges: ";
more_clear_headers "Content-Length: ";

That causes the error on my side. I just deleted it and restart nginx and everything works as expected. Basically, Jason gives me the hint (top class @Jason)

Thank you so much for sharing Ken. I really appreciate it. Cheers!
·
Wednesday, 12 November 2014 17:35
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Neel ,

Glad to heard your guys issues resolved.
·
Thursday, 13 November 2014 12:48
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post