ASP.NET adds an extra info at the end of the URL. How to avoid it?

Question

In an ASP.net website, the link to

http://scarab.ineo.be/Catalog.aspx?id_rayon=0000000015

is redirected automatically to

http://scarab.ineo.be/Catalog.aspx?id_rayon=0000000015#.Uyr5GPnWWi0.

Why is #.Uyr5GPnWWi0 added ?

I thought it was something regarding the sessionState. In the web.config, the sessionsState is

<sessionState mode="SQLServer" sqlConnectionString="data source=....\SQL2008R2; integrated security=false; user id=sa; password=...." />

Is it possible to avoid this extra info at the end of the URL ?

I dont get the additional hash in the query string when i navigate to your URL's — matthijsb, Mar 20 '14 at 14:25

Phill · Accepted Answer · 2014-03-20T14:41:22.527

3

That looks nothing like a sessionState issue, it looks EXACTLY like the AddThis plugin hash for tracking...

http://support.addthis.com/customer/portal/questions/352733-how-to-remove-hash-from-url-

If you're using AddThis it will add a hash to all links. You can turn this off by adding the following JavaScript:

<script type="text/javascript">
var addthis_config = addthis_config||{};
addthis_config.data_track_addressbar = false;
</script>

Edit:

I just took a look at your website, and you are using AddThis. You also have the following code in your page:

<script type="text/javascript">    var addthis_config = { "data_track_addressbar": true };</script>
<script type="text/javascript" src="//s7.addthis.com/js/300/addthis_widget.js#pubid=ra-510a8b7d07484835"></script>

Notice how you have the config for addressBar tracking set to true.

You need to turn this off.

edited Mar 20 '14 at 14:41

answered Mar 20 '14 at 14:34

Phill

18,398
7
62
102

1

I have to agree that it does seem a short querystring for cookieless... perhaps you are right! – JP Hellemons Mar 20 '14 at 14:36
1

Just took a quick look at his site, hes using the AddThis plugin. – Phill Mar 20 '14 at 14:39
You are 100% right : data_track was used and setting data_track_addressbar to false fixed this issue. Thanks a lot. – Mar 20 '14 at 15:56

score 1 · Answer 2 · edited May 23 '17 at 11:43

1

It has to do with the sessionstate. Normally Asp.Net webforms handles this by setting a cookie. So that the server side can determine which user is which.

But if you have sessionState in the web.config configured to be cookieless, it will append a random string to each url to identify the users session.

http://msdn.microsoft.com/en-us/library/h6bb9cz9%28v=vs.85%29.aspx

How does ASP.Net Cookieless work ?

edited May 23 '17 at 11:43

Community

1
1

answered Mar 20 '14 at 14:28

JP Hellemons

5,977
11
63
128

1

Just for the record cookieless sessions are serious security risk. Avoid! – Stilgar Mar 20 '14 at 14:31
Totally agree @Stilgar it is a bad practise. – JP Hellemons Mar 20 '14 at 14:35

ASP.NET adds an extra info at the end of the URL. How to avoid it?

2 Answers2