Alright, fair enough. Hash-Bang URLs are quite special. but that doesn’t make up for the fact that routeros webproxy ignores everything after the hash all together. we are not talking about caching those pages and the challenges to do so, we’re talking about a simple access rule not working because of that. some very popular sites are using that method and it appears to be becoming more and more like a common practice.
Like you see in the article, it’s exactly the point of these URLs. Even web browsers consider everything after the hash, to be the same page, and ignores it.
Ok. i did a bit testing with Web debugger tools. this does seem to be very special. ill do more study on this matter when i got time. thanks for pointing it out
Alright, i did a bit of research on how Orkut communicates with its server. to block that profile, you need to block a POST request being sent to http://www.orkut.com/gwt/Multiplexer , with specific data in it. i don’t think web proxy could do that. your best chance is probably L7 (or maybe ‘Content’ in firewall rule?). see the attachment for the detail.