| 7:37 am on Feb 3, 2014 (gmt 0)|
What have you tried so far?
:: insert Why We Make You Do It Yourself * boilerplate ::
|On accessing "http://126.96.36.199/~username" it will redirect to |
Do you mean that it currently does redirect to ... or that you want it to redirect to ...?
Also: is ~username one specific name, or do you want to capture and reuse a variety of names? Or recognize a variety of names and not capture them? (But if so, how will users be able to carry on where they left off after they've logged in?)
* This really exists. I wrote it up a couple of years ago. But it tends to make people mad. Um, madder than they were already.
| 8:02 am on Feb 3, 2014 (gmt 0)|
~username one specific name. No need to capture and reuse. But the URL after the username. ~username/xxx. There xxx should be captured and redirected to ip/xxx.
>>On accessing "http://188.8.131.52/~username" it will redirect to
Yes. It currently redirects. And it should also work fine.
| 8:41 am on Feb 3, 2014 (gmt 0)|
Now, wait. What URL after username? What's the pattern? Something was missing from the first post.
Anyway, original question stands. What have you tried so far, and what (exactly) happens when you try it?
| 8:54 am on Feb 3, 2014 (gmt 0)|
The pattern is "http://184.108.40.206/~username/verification.php". It should go to "http://220.127.116.11/verification.php".
I have googled for rules and tried something. Nothing works. I am a noob in this. Can you please tell what rules should I use?
Consider that nothing done. I got nothing in internet to redirect from the format "ip/~username".
| 4:39 pm on Feb 3, 2014 (gmt 0)|
|and tried something. Nothing works. |
If you won't say what you've tried, there's no way to know what went wrong.
:: detour to haul out boilerplate ::
|Why We Make You Do It Yourself |
There are plenty of forums where you can post a "how-to" question and get a fairly immediate answer. The answer may even be correct. But WebmasterWorld is about teaching you how to do it yourself. That way you can roll your own htaccess-- not just for today's problem but for tomorrow's almost identical one.
Here is the analogy:
Your child's room needs cleaning. You know that you can clean it yourself much faster and better than if you have to stand over your child and force him to do it right. But if you do the "make him get it right" part often enough, you will have raised a child who knows how to clean his room-- and who will some day stand glowering over his own children in the same circumstances.
Some day, someone else will post a question in the WebmasterWorld forums and you'll say "Hey, I know the answer to that one!"
I left out one paragraph which doesn't apply to you.