• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • paul wheaton
  • Ron McLeod
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Carey Brown
  • Piet Souris
Bartenders:

A "nice" online reservation web site

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,

Please, can someone give an advice on www.airalgerie.dz, i discover this online reservation web site and i was surprised by the design:
-session state is stored in the client side: hidden fields are heavily used
-navigation flow between jsp pages is managed by...... javascript code
-errors messages for validation are...."pretty too explicit"

Any comments?
Thanks
Albert
 
Ranch Hand
Posts: 39
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
My 2 cents: By exposing everything to client side including navigation flows and hidden fields opens site up for spoofing.

I would say security will be my top concern with this kinda approach.
 
Greenhorn
Posts: 26
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I thought about similar approach. Client side state can be kept to a minimum: just primary keys of things like airports, flights, seats, etc referenced in current itinerary. Whole structure can be serialized into few hundred bytes (well within 4K cookie limit).

Regarding security, whole interaction can go over HTTPS. Payment submission form must use some kind indirect way of credit card identification anyway.

Also, whole session-containing cookie/hidden field can be encrypted/signed.

Now think about web-tier state. Hacker can intercept somebody's JSESSION_ID and book some flights. Unless... :-)

Regards,
Andy
 
reply
    Bookmark Topic Watch Topic
  • New Topic