HTTP redirect

Bug or feature?

Hacking/redirecting the nondefault HTTP port works as if one had hacked the default HTTP port (the hacker gets the money).

This is the end of the HTTP shell game ^^
http://en.wikipedia.org/wiki/Shell_game

I had 2 HTTP ports open. port A was well defended , watched and default. Port B was undefended and unwatched.
Both were non dummied.
Port B was opened for testing.
Someone hacked for testing port B.
A few minutes later he got my HTTP payment.
He didn't attack my default HTTP port before

It makes sense that the last redirect of any HTTP will work. (gaming sense)
Bank ports dont really need a default port anymore if taken the new banking interface in account. depositPettyCash() was announced to use the bank script of the watched port (what if it watches a non bank port?). Same might be for sendMoney() as it is a watch function too.
Attack Scripts have no use for a default port too.
FTP scripts need it - until the FTP transfer window is extended with a source and target port box.
HTTP needs it to choose which script controls the webpage.

The functions
getDefaultBank()
getDefaultFTP()
getDefaultAttack()
getDefaultHTTP()
counterattackAttack() //attacks the default Attack port of the attacker !=counterattack()
counterattackBank() //attacks the default Bank port of the attacker
would become useless.