mmn-20150331-ostatus-b4ry.html
Error showing notice: File not found in filesystem.
@mmn @andstatus ...and even the #nginx "solution" looks like a dirty hack. "on error, go to a page that doesn't treat it as an error!". HTTP/1.1 describes "411 Length Required" as "The request did not specify the length of its content, which is required by the requested resource". If the resource requires it - the solution is not to add a hack on the resource side but instead to supply the missing information. I.e. the "Content-Length" header. Whi…
Tuesday, 31-Mar-2015 16:46:38 CEST
permalink
Attachments
mmn-20150331-ostatus-wgfu.html
Error showing notice: File not found in filesystem.
@andstatus Maybe Twitter - a single server environment - has implemented this hack too. But we can't all do it. And we're not all going to switch to nginx. So I guess you haven't tried sending the Content-Length yet. I'll ignore this thread until I know it has been tested and failed. You're welcome to send me the .apk of a test build which sends that header if you still experience problems (which likely won't be "411" errors).
@andstatus I have explained this on github. quitter.se is NOT running fastcgi. I don't know what loadaverage and vinilox is running. Several sites running fastcgi has confirmed to not work with chunk, at least the version they are running. What would be nice if you could try is to set the content-length in the header, which should be a easy job? /cc @mmn @mmn@social.umeahackerspace.se
@andstatus Different webservers and configs. https://social.mxchange.org/url/4126 runs Apache with mod_php - that does _not_ use CGI. https://social.mxchange.org/url/7372 runs nginx v1.6.2, maybe he has even applied the config fix? I don't know about @vinilox@status.vinilox.eu but I would guess he runs a similar config to #quitter.se The nodes where "411 Length required" come up run some form of fastcgi (php5-fpm uses the fastcgi interprocess …
Tuesday, 31-Mar-2015 19:53:06 CEST
permalink
Attachments
mmn-20150331-ostatus-gpju.html
Error showing notice: File not found in filesystem.
@knuthollund You can see which webserver software they use (but not how PHP is loaded, only which version) by running 'curl -I domain.com' :)
@andstatus Sorry, I was going to ignore this thread until sending the Content-Length header from AndStatus has been attempted.
As I understand now, lack of chunked encoding support is a real cause of this incompatibility. Chunked encoding is used exactly when content length is unknown beforehand. As suggested here: https://social.mxchange.org/url/31085 , switching to HTTP 1.0 protocol reliably turns this feature off, and this will ensure compatibility with different legacy/"simple" server implementations. I will test this and will add corresponding compatibility option to the Social n…
Wednesday, 01-Apr-2015 08:16:39 CEST
permalink
Attachments
andstatus-20150401-ostatus-qpjx.html
Error showing notice: File not found in filesystem.
@andstatus@loadaverage.org It could perhaps also be possible according to various internet sources to just supply a content-length of 0 and still use chunked transfer. Untested though. But if your library (apache.httpclient?) doesn't let you, I understand your problem.
I succeeded in posting a message with an attachment to https://social.mxchange.org/url/1873 . This required two changes: 1. Set apache HttpPost request to HTTP 1.0 protocol: HttpPost request; ... request.setProtocolVersion(HttpVersion.HTTP_1_0); When creating Multipart post request I'm providing as an input for an attachment not a InputStream (as for HTTP 1.1, which causes chunked encoding), but an array of bytes, which I have to create from the same stream bef…
Thursday, 02-Apr-2015 07:57:08 CEST
permalink
Attachments
andstatus-20150402-ostatus-ftdj.html
Error showing notice: File not found in filesystem.
Why not just an automatic fallback? If you get the 411 error, you send it with HTTP/1 @andstatus@loadaverage.org
If the _client_ users have to track the _server's_ behaviour it will just cause confusion. The client app should automatically fall back to whatever works so when the server fixes its problem all the client users don't have to configure a setting which they don't even understand the meaning of. @andstatus@loadaverage.org
@mmn@social.umeahackerspace.se As we discussed already regarding "SSL Mode" in AndStatus, indeed, it would be good for a client application to adapt to a server automatically. But as for an "SSL Mode", for the second option: "Use legacy HTTP protocol" - automatic discovery _during normal operation_ of a proper connection option is not practical. Because this will mean substantial time delays and network traffic increase. E.g. in this "411-content-length-r…