ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting.

Start putting together a set of guidelines that could help address the security issues triggered by links rewriting.

State:
closed
Person:
Robert Finean
Due on:
December 23, 2008
Created on:
December 16, 2008
Associated Product:
Guidelines for Web Content Transformation Proxies
Related emails:
  1. [minutes] F2F Day 2 - 26 March 2009 - Content Transformation Guidelines (from fd@w3.org on 2009-03-30)
  2. RE: ACTION-902 (Reprise) Summarise and prepare proposed resolutions on HTTPS link rewriting. (from jrabin@mtld.mobi on 2009-03-20)
  3. RE: ACTION-902 (Reprise) Summarise and prepare proposed resolutions on HTTPS link rewriting. (from SPatterson@Novarra.com on 2009-03-19)
  4. RE: ACTION-902 (Reprise) Summarise and prepare proposed resolutions on HTTPS link rewriting. (from BS3131@att.com on 2009-03-19)
  5. RE: ACTION-902 (Reprise) Summarise and prepare proposed resolutions on HTTPS link rewriting. (from jrabin@mtld.mobi on 2009-03-19)
  6. Re: ACTION-902 Summarise and prepare proposed resolutions on HTTPS link rewriting. (from jrabin@mtld.mobi on 2009-03-11)
  7. ACTION-902 Summarise and prepare proposed resolutions on HTTPS link rewriting. (from jrabin@mtld.mobi on 2009-03-09)
  8. Re: ACTION-893: ... the security issues triggered by links rewriting. (from passani@eunet.no on 2009-02-04)
  9. Re: ACTION-893: ... the security issues triggered by links rewriting. (from tom.hume@futureplatforms.com on 2009-02-04)
  10. Re: ACTION-893: ... the security issues triggered by links rewriting. (from chaals@opera.com on 2009-02-04)
  11. Re: ACTION-893: ... the security issues triggered by links rewriting. (from tom.hume@futureplatforms.com on 2009-02-03)
  12. Re: ACTION-893: ... the security issues triggered by links rewriting. (from passani@eunet.no on 2009-02-03)
  13. Re: ACTION-893: ... the security issues triggered by links rewriting. (from chaals@opera.com on 2009-02-03)
  14. RE: ACTION-893: ... the security issues triggered by links rewriting. (from jrabin@mtld.mobi on 2009-02-03)
  15. Re: ACTION-893: ... the security issues triggered by links rewriting. (from tom.hume@futureplatforms.com on 2009-02-03)
  16. Re: ACTION-893: ... the security issues triggered by links rewriting. (from chaals@opera.com on 2009-02-03)
  17. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from passani@eunet.no on 2009-01-21)
  18. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from passani@eunet.no on 2009-01-21)
  19. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from Tom.Hume@futureplatforms.com on 2009-01-20)
  20. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from Tom.Hume@futureplatforms.com on 2009-01-20)
  21. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from passani@eunet.no on 2009-01-20)
  22. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from Tom.Hume@futureplatforms.com on 2009-01-20)
  23. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from passani@eunet.no on 2009-01-20)
  24. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from Tom.Hume@futureplatforms.com on 2009-01-20)
  25. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from Tom.Hume@futureplatforms.com on 2009-01-20)
  26. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from casays@yahoo.com on 2009-01-20)
  27. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from fd@w3.org on 2009-01-20)
  28. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from jalberto@cellectivity.com on 2009-01-20)
  29. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from passani@eunet.no on 2009-01-20)
  30. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from jalberto@cellectivity.com on 2009-01-20)
  31. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from passani@eunet.no on 2009-01-20)
  32. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from dstorey@opera.com on 2009-01-20)
  33. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from Tom.Hume@futureplatforms.com on 2009-01-20)
  34. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from passani@eunet.no on 2009-01-20)
  35. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from casays@yahoo.com on 2009-01-20)
  36. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from fd@w3.org on 2009-01-20)
  37. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from passani@eunet.no on 2009-01-20)
  38. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from dstorey@opera.com on 2009-01-20)
  39. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from passani@eunet.no on 2009-01-20)
  40. [agenda] BPWG 2009-01-20 (Tomorrow) *REMINDER* This is the main BP call switched to Tuesdays (from jrabin@mtld.mobi on 2009-01-19)
  41. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from fd@w3.org on 2009-01-19)
  42. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from passani@eunet.no on 2009-01-18)
  43. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from dstorey@opera.com on 2009-01-18)
  44. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from passani@eunet.no on 2009-01-18)
  45. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from dstorey@opera.com on 2009-01-18)
  46. RE: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from rotan.hanrahan@mobileaware.com on 2009-01-18)
  47. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from passani@eunet.no on 2009-01-18)
  48. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from dstorey@opera.com on 2009-01-18)
  49. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from passani@eunet.no on 2009-01-18)
  50. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from dstorey@opera.com on 2009-01-18)
  51. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from passani@eunet.no on 2009-01-18)
  52. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from Tom.Hume@futureplatforms.com on 2009-01-18)
  53. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from passani@eunet.no on 2009-01-18)
  54. RE: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from rotan.hanrahan@mobileaware.com on 2009-01-17)
  55. Re: ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from Tom.Hume@futureplatforms.com on 2009-01-17)
  56. ACTION-893: Start putting together a set of guidelines that could help address the security issues triggered by links rewriting. (from Rob.Finean@openwave.com on 2009-01-16)
  57. [minutes] CT call 16 December 2008 (from fd@w3.org on 2008-12-16)

Related notes:

No additional notes.

Display change log.

Jo Rabin <jo@linguafranca.org>, Daniel Appelquist <daniel.appelquist@vodafone.com>, Chairs, Dominique Hazaël-Massieux <dom@w3.org>, François Daoust <fd@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 893.html,v 1.1 2011/01/10 15:19:29 dom Exp $