Currently SWeTE requires you to set up a proxy for a specific URL including port number and protocol. This means that the base site can be either http or https but not both. This causes problems on sites that use HTTP most of the time but may redirect to https when it needs to perform secure things. In these cases, SWeTE would redirect to the base site rather than just translate the secure page.
Note: This is the safest behaviour as it prevents swete from inadvertently being a middle man for secure transactions.
On the other hand it may be desirable at times to have SweTE automatically adapt to different protocols.
Currently SWeTE requires you to set up a proxy for a specific URL including port number and protocol. This means that the base site can be either http or https but not both. This causes problems on sites that use HTTP most of the time but may redirect to https when it needs to perform secure things. In these cases, SWeTE would redirect to the base site rather than just translate the secure page. Note: This is the safest behaviour as it prevents swete from inadvertently being a middle man for secure transactions.
On the other hand it may be desirable at times to have SweTE automatically adapt to different protocols.