Bitzu

CPSA ยท Web servers, architecture and protocols

Thin and thick web clients, applets and decompilation

Servlets, Java applets, ActiveX, Flash, .NET thick clients and decompiling client-side code.

Key points

  • Thin client: browser rendering server HTML. Thick client: real logic, often its own protocol or API.
  • Servlets: server-side Java, not client code.
  • Legacy client code: Java applets, ActiveX (Windows, Internet Explorer era), Flash (end of life 31 December 2020).
  • Java bytecode and .NET assemblies decompile to near-readable source, exposing hard-coded keys, endpoints, alterable checks.
  • Never trust client logic or embedded secrets.

Source: https://www.adobe.com/products/flashplayer/end-of-life.html

Practice questions

Single choice

Where does a Java servlet execute?

  1. In the user's browser
  2. On the server, inside a servlet container
  3. On the user's graphics card
  4. Inside the DNS server
Show answer

Answer: B. On the server, inside a servlet container

Servlets are server-side Java components run by a servlet container. Applets, not servlets, were the browser-side Java.

Select all that apply

Which of these are legacy browser-delivered client technologies?

  1. Java applets
  2. Flash
  3. Servlets
  4. CGI scripts
  5. HTTP status codes
Show answer

Answer: A. Java applets, B. Flash

Java applets and Flash were downloaded and run in the browser. Servlets run on the server, and plain HTML forms are standard markup, not plug-in code.

True or false

True or false: obfuscating a client application makes embedded secrets safe to ship.

Show answer

Answer: False

False. Obfuscation only slows analysis; the client must still run, so the secret can be recovered. Sensitive checks and keys belong on the server.

Practice 8 questions on this topic in Bitzu

Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.

Download on the App StoreGet it on Google Play

More CPSA topics in this module