Limits of the TS2 webserver

[Label2021]

I noticed that the TS2 webserver used for webadmin, is very strange indeed. It has its login post to some virtual file called login.tscmd, which is limiting me from accomplishing a task I need. I simply wanted to turn the super admin login page into a php script (still posting to login.tscmd) so that I could add extra security for my superadmin login. Now if I had good php coding skills and an understanding on how webadmin works the way it does, I would be able to accomplish this by making my own webadmin possibly, but this is not the case.

As soon as I turn my slogin.html to a slogin.php with extra php coding, the TS2 webserver has a default way of redirecting to login.html if something looks weird, and that it does. So, is it in any way possible to get the webadmin werbserver to support php, or to somehow make a TeamSpeak module to allow an instance of Apache on any given port, to actually work with the TS2 server? If not, then I HIGHLY recommend this support into TS3.



-LabeL-

[Label2021]

*bump*

I would guess this is not a possibility?

[Broder]

Hmm...

I haven't tried it but what if you try the following

1. Rename slogin.html to slogin1.html
2. Create a file called slogin.html
3. from within slogin.html call any php file you want
4. When that php script is finished send the User to the file you renamed in 1

Not really secure as someone could guess the renamed file but I am sure you could come up with some weired name ;-)

Alternatively you could move the Port of the Webinterface to something completely different from the Standard too.

As I said I haven't tried it but I guess it would work.

[Label2021]

SOrry, im not very fluent with PHP, but I knew enough of it to limit a slogin.php to certain IP's (which is what I was trying to acheive) I am not sure how to call a PHP script from an html file. And not to mention, when trying to access any non-standard file through webmind (httpdocs folder) it automatically redirects to login.html no matter what. I can basicly copy slogin.html to a file called slogin2.html and when trying to access this new file it would say "I dont think so..." and redirect automatically to login.html even if it was a valid file in the first place. So even then, this idea wouldnt work as far as I can tell.

It would just be better, if someone made a PHP or some other type of webadmin that strictly uses TCP to handle its administration. Would work wonders, along with more options to things.



-LabeL-