Take the 2-minute tour ×
Stack Overflow is a question and answer site for professional and enthusiast programmers. It's 100% free, no registration required.

I am using WIF and a federated security model using ThinkTecture STS.

When I try to request the url: http://domain.com/#page, WIF is not redirecting to the correct page after authentication.

The ru param in wctx does not contain the correct path of /#path. Instead it ignores the hash and everything after it, so the ru param is just /. A normal url without a hash works fine.

Is there a workout around for this or am I formatting my url incorrectly?
Any suggestions?

share|improve this question
add comment

2 Answers

That's the whole point of hash fragments - that they don't end up on a server.

share|improve this answer
add comment

It looks like its the browser that isn't sending the hash part of the url back to the server. I believe this is a HTTP standard, as the hash part was originally only intended for client side anchor tagging.

There are workarounds using ajax/javascript, but as I am using a simple GET request, it would appear impossible.

See these similar questions, which explain the problem...

How to get Url Hash (#) from server side

do browsers remove # in URL automatically?

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.