I have a web application that uses url which looks like this:
< / P>
(The GUID is used to discourage a mistake instead of a simple int, which is what we need to do now.)
Problem: When sent by email, that long URL is often broken This person is sending emails, so I can not control formatting. Occasionally sending an email program is a mistake, sometimes it is received, but I am spending a lot of time talking to people through fixing problems.
Everything should be done from this domain, so I can not use it. I can host a third party shorter, but it seems that Kuldz.
Any suggestions?
Editing
@Sunny: Thank you wide, but my situation is different from what you believe. A corporate customer (mine) passes his staff to this urc, and they use it to reach the branded registration page. As part of the registration they will have to give a working email, and it will be sent to the corporate supervisor.
Registration gives them access to a database, but the interlocutor is sometimes not a great deal if they do not see anything specific to the corporate customer; When they get out of the corporate supervisor, we invite them to invite them. ? & Amp; = ), but on some pre-determined line-length I was surprised too, very note that the domain name is long, as is the path of the virtual directory, which is a part of the problem.
After reading the responses, I am going to use Base 64 as a pseudo-shorter, like something:
... and See if he's alive. Thanks to all.
You can at least make it a little smaller. Now, you can send a GUID, which is a 128-bit number, in a format that is hexadecimal with an additional dash, if you see the GUID as a byte array and convert it to Base64, then you Some things can be cut down. Similarly, "query = academic" can be "q = a".
The GUID is currently taking 36 characters. Changing to base-64 can reduce it to 22, 14 characters are being saved. Changing "Query = Academic and Key =" with "Q = a and amp; k =" 13. To reduce the total 27 characters, your URL should not be enough to keep it short, while the empress and the same sign Despite the presence. / P>
Another extension: Base-64 text is ending with "=", which will then be hex-encoded in "% 3d". The solution is to cut that character, because it is just padding.
With the credit to the original poster, it seems that the best bet is a combination of things:
- Compact GUID with base-64
- Minimize key names and, if possible, value.
- To encourage the URL in the angle field to parse the client properly.
- If possible, replace the key names with a URL-retype, so that it looks like a path.
Comments
Post a Comment