Project

General

Profile

Actions

Feature #2192

closed

file upload from SWFUpload using Adobe flash player (Linux version)

Added by Andymeows almost 15 years ago. Updated almost 15 years ago.

Status:
Invalid
Priority:
Normal
Category:
core
Target version:
-
ASK QUESTIONS IN Forums:

Description

I'm trying to use SWFUpload with my lighttpd server, but lighttpd is returning an HTTP 400 response when using the Linux version of the Flash player. The reason this is happening is because when it sends the HTTP request, the User-Agent header is missing a carriage return (0x0d) at the end of the line. I realize that this is not really a bug in lighttpd, and that the CRLF is specified in the HTTP protocol, but I believe this is working in Apache. This totally goes against protocol, but it would be nice to be able to allow this as an option to not require the carriage return in the message headers.

...
Accept: */*\r\n
User-Agent: Shockwave Flash\n
Connection: Keep-Alive\r\n
...

Actions #1

Updated by usef almost 15 years ago

This issue is a great gift Adobe has done only to Linux version of Flash player.
If you try with Windows or Mac Osx, you can see that the carriage returns are managed in the correct way.

Anyway seems that with the 10.1 version of the player the problem will be resolved.

Apache doesn't have this problem, but I don't think it does a strict control over the Http Protocol as Lighty does.
And I really don't think the dev will implement an option to override the protocol just for an Adobe bug. ;)

Y.

Actions #2

Updated by icy almost 15 years ago

  • Status changed from New to Invalid

Correct, we will not work around bugs in broken clients. Adobe is the one who has to fix it (and seems like they finally did?).
Otherwise we might introduce bugs ourselves because noone knows what allowing a single \n might break...

Actions

Also available in: Atom