is there a way to configure redirects? about of-watchdog HOT 4 CLOSED

Hi @pyramation thanks for your help with this 👍

The feature/fix is release and generally available.

Alex

from of-watchdog.

Example to reproduce the behaviour:

"use strict"

module.exports = (event, context) => {
  context
    .headers({'Location': 'https://www.google.com/'})
    .status(307)    // Temporary
    .succeed('Page has moved.')
}

With the Node template.

The Golang code in of-watchdog proxies up the Node HTTP process which tells it to redirect to i.e. google.com - so that's what the proxy does, it fetches the site Node is telling it to fetch.

That's why you're seeing this.

I'd be curious to see what happens if you try using a "stateless microservice" with OpenFaaS - i.e. your own Dockerfile + Node / Express server - https://www.openfaas.com/blog/stateless-microservices/

from of-watchdog.

We'd have to update the Golang proxying code to support this.

This is how I did it for the auth service in OpenFaaS Cloud - I needed the router to pass back the redirect instruction to the client’s browser. https://github.com/openfaas/openfaas-cloud/blob/3d3ed09707817b436751b279973d6f26191930a4/router/main.go#L34

cc @LucasRoesler

from of-watchdog.

I just added an example repo with a bare microservice (as @alexellis suggested) here https://github.com/pyramation/redirect-openfaas-example

Here are my results:

My first route (just a text response) is A-OK:

The redirect route, seems to work in sinatra, but not the browser:

from of-watchdog.