No content-type header for requests checking for cache expiration (304) about serverless-http HOT 4 CLOSED

Youre suggesting that we should not ask about binary if there's no content type?

from serverless-http.

Currently, 304 requests processed wrong, responses have application/json Content-Type?
Anyways I resorted into disabling etag in ExpressJS, resulting in no If-modified-Since sent by browser.

I think If-Modified-Since must be handled differently. Of course binary must be called only if ExpressJS actually give out body in handler.

// Disable 304 support, works wrong IMO
app.set('etag', false);
// Always send last-modified as current time
app.get('/*', function(req, res, next){ 
  res.setHeader('Last-Modified', (new Date()).toUTCString());
  next(); 
});

https://github.com/huksley/todo-react-ssr-serverless/

from serverless-http.

Just a thought...
Maybe we can do the following:

• by utilizing serverless-webpack, gather all links to static resources (imported)
• gather all static resources in public/ and other folders
• deploy them to S3 public bucket
• for every resource, define API GW proxy endpoint during deploy

This way, all static resources will be handled by S3 bucket

P.S. best way is to skip API GW entirely and serve them from S3 bucket/CDN directly

from serverless-http.

I mean yeah that sounds like something that could be a serverless plugin - it's def. out of scope for this library.

For the content-type stuff, it's always good to just set up an express app first and verify how it behaves, on its own.

from serverless-http.