Actually, inserting a user's password in a URL is very insecure -- pwnd!
the right way is to log a customer in and use an expiring token -- one time use.
any authorization printed into HTML is a hijack -- bad idea all around.
sure it is ...
<div class="verify-iframe>
if you owned the domain you would have no problem ...
explain what you need to do ...
no parameter double talk ...
Welcome to Our Community
Wanting to join the rest of our members? Feel free to sign up today.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Attention: "role based name" email prefixes such as support, webmaster, info, contact, forum, service, affiliate, admin, traffic, partners, marketing, etc., for our member accounts are not permitted. They are acceptable for a vendor listing, but not for the member email. This is due to bulk email processors scrubbing them for delivery due to extremely high bounce rates. Please apply for membership using a personalized email prefix. Something like bob@xxxxx.com.
If we discover you signed up with a role based name we will give you only one message to change it. After 3 days your account will be removed if the email is not changed.