Now what LinkedIn doing was adding ‘#!’ (called shebang or hashbang) turning it into:
The part of url after # in Google Plus is used for redirection and when Google Plus sees the exclamation mark after the hash it just doesn’t know what to do and redirects to the following 404 page:
What I learned from a stack overflow question was that the part of the url after hash is never sent to the server. I confirmed that with curl. The problem was finding out how to avoid this from happening.
I tried using some redirectors like gplus.to and the shebang was still sent all the way to google plus. I tried using my Google+ short url +OmerCanKaradagli and Google+ still parsed # and redirected to the same 404 page.
I then found out something on LinkedIn redirector. It doesn’t add shebang when the URL already has a hash in it! I thought I can use this considering Google+ uses hash to do redirects. So I used the following:
I noticed the issue with this the next day. Google+ home page can only be accessed by those that are logged in to Google+!
I found out something on LinkedIn redirector. It doesn’t add shebang when the URL already has a hash in it! I thought I can use this considering Google+ uses hash to do redirects. So following is the end result:
What are those long numbers?
To those who might not know, those long number at the end of the URL are Google+ profile IDs. The first number just after the forward slash is profile ID of LinkedIn page. The one after the hash is my profile ID. If you have your Google+ URL like google.com/+YourName, it might not be easy to find. To get it, you will need to hover over the your name in any of your posts.