36809 Mensajes en 36772 Temas - por 3472 Usuarios - Último usuario: AHSEarnest

* Chat Sentinela

Refresh History

Autor Tema: バーバリー 財布 Ajax deep linking compatibility  (Leído 53 veces)

hdjpluluazb

  • Jr. Member
  • **
  • Mensajes: 80
    • Ver Perfil
バーバリー 財布 Ajax deep linking compatibility
« en: Mayo 05, 2013, 10:03:20 am »
Ajax deep linking compatibility バーバリー 財布
You'll need to try and ensure that when people link to the site, they use the hardcoded deeplink rather than the hashed deeplink
I don't recommend ever using the query string as you are sending data back to the server without direct relevance to the prior specified destination エルメス 時計. That is a corruptible security hole as malicious code can be manually added to the query string to cause a XSS or buffer overflow attack at your webserver ポールスミス バッグ.
I believe REST was intended to work with absolute URIs without a query string バーバリー バッグ, because then your specifying only a location of a resource and it is that location that is descriptive and semantically relevant in addition to the possibility of the resource being so equally relevant プラダ 公式. Even if there is no resource at the specified path you have still instantiated a potentially unique and descriptive location that can be processed accordingly バーバリー.
As you said in the question, there's no way for the server to know about the URL fragment so filtering would not be applied for users without JavaScript enabled if they were given a link to /clothes#filter.
However ヴィトン, even without filtering シャネル ネックレス, these links could be made more meaningful for non-JS users by using the filter strings as IDs in your /clothes page hermes. To prevent this messing with the Ajax experience the IDs would need to be changed (or the elements removed) with JavaScript before the Ajax links were initialised プラダ.
Related articles:
 
 
   ヴィトン 公式 gooder to cash out
 
   ヴィトン Cellulite Structure
 
   プラダ 公式 39289
 
   chanel 31589
 
   グッチ バッグ 17093

 

SimplePortal 2.3.4 © 2008-2011, SimplePortal