В тех поддержке сослали на форум где написали
login.html:
Code:
<html><head>
<meta http-equiv="refresh" content="0; url=login?username=myUsername&password=myPassword">
<meta http-equiv="pragma" content="no-cache">
<meta http-equiv="expires" content="-1">
</head><body></body></html>
login.html is the page loaded to show the login form. The above is a simple meta refresh that causes the browser to submit pre-determined credentials to the login servlet, in this case for the user 'myUsername' with a password of 'myPassword'. As long as that account with that credentials exists in the local user database (or via RADIUS) the user will be automatically logged in.
alogin.html:
Code:
<html><head>
<meta http-equiv="refresh" content="0; url=http://www.google.com">
<meta http-equiv="pragma" content="no-cache">
<meta http-equiv="expires" content="-1">
</head><body></body></html>
alogin.html is loaded after a successful login. In this case, it will trigger a redirect to Google by merit of a similar meta tag.
From the user's perspective they open a browser, and half a second later Google appears. From the router's perspective a normal, full log on took place for the 'myUsername' account.
http://wiki.mikrotik.com/wiki/Manual:Cu ... t#Examples also contains an example that will do this via JavaScript.
In my experience JavaScript is supported by fewer devices - usually most devices support it but some users disable it - so while JavaScript is technically cleaner than abusing a meta refresh like above, meta refreshes get the desired result for more users.
Кто может подсказать что с этим делать?:)