Allow multiple hosts filtering about cassette HOT 8 OPEN

we know that possibility to use request.host but this is not a good pratice, and can cause security issues.

from cassette.

We could add multiple hosts in the config.yml and then we could use the request.host as the service for validation, but verifying if the service is in the config.yml.

WDYT?

from cassette.

suggestions:

• build a more specialized controller filter for this use case
• provide a separate configuration entry for the "alternative" services so current configs don't break

from cassette.

@ricardotealdi This can be a cool approach, we can auto detect the service key value type, and assume a default beheviour.

from cassette.

+1

from cassette.

When there are multiple hosts actually the cache doesnt work, for example:
Im authenticating with first host and generate some ticket, if i try to authenticate again with the same ticket but another host the ticket will be valid cause its in the expire time.

from cassette.

@fagnerpereira Great point! There is a bug on the ticket caching. Even if we implement something to allow for multiple hosts, the ticket caching won't validate a different service/host.

from cassette.

The ticket just be valid with our service, the cache key will should be a hash of key+service :p

from cassette.