serverless-devs / fc-http Goto Github PK

https://github.com/devsapp/nodejs-runtime-fc

https://www.npmjs.com/package/serverless-http

如图，使用 koa框架构建服务的时候引入 koa-static，除了图片其他静态资源都可以正常渲染，

when trying to return a binary file (20KB) to the caller. Caller side received corrupted binary file (35KB).
test-fc-http.zip

can be repro using attached modified sample project. under GET /file/:filepath endpoint.

to repro, try calling GET /file/data.jpg
the return image file becomes invalid.

no problem when returning text files.

have tried to set the binary flag as such, but none of the suggested options solve the above issue.

// option 1:
exports.handler = serverless(app);

// option 2:
exports.handler = serverless(app, {
  binary: false     // true / false doesn't matter, problem still exists
});

// option 3:
exports.handler = serverless(app, {
  binary: ['image/*', 'application/octet-stream']
});

I would usually get the remote IP from value of req.headers['x-forwarded-for'] when my code is running in FC custom runtime.

but when using the Nodejs runtime via the fc-http wrapper, this value is undefined.

it would be good if it can be consistent with the usage of other runtimes like FC custom (I can also get it when running in AWS lambda through the serverless-http wrapper).

if not, what is your advice on how to get it (preferably an official method that will be persistent in future implementations).

response.status = data.statusCode;

response里面有status这个属性吗？我觉得上述代码要改成这样吧

response.statusCode = data.statusCode;

https://github.com/devsapp/start-web-framework/tree/master/example/todolist-app/src

Hi, was trying to upload binary file through multipart formdata to an Express endpoint that is wrapped by the fc-http.

for example, when a png file (27110 bytes) was uploaded, the service end received a file that has a size of 47553 bytes.

I have modify the Express example slightly to repro the issue, see attached zip.
test-fc-http.zip