diff --git a/README.md b/README.md
index 928b026..251a51e 100644
--- a/README.md
+++ b/README.md
@@ -347,3 +347,17 @@ recent and largely contained to Envoy, which already supports B3 single format.
 Sending a larger second header would increase the pain to others who don't have
 this problem anyway. Put another way, the few proxies missing B3 single header
 support should update instead of burdening more people from lack thereof.
+
+# Showcase: propagation from an Apache reverse proxy
+
+Zipkin users were <a href="https://github.com/openzipkin/zipkin/issues/1479">wondering</a> 
+if it is possible to start B3 propagation from an Apache reverse proxy. [adammichalik](https://github.com/adammichalik)
+came up with a <a href="https://github.com/openzipkin/zipkin/issues/1479#issuecomment-682639979">clever</a> 
+way to accomplish this, using Apache modules only:
+
+```
+RequestHeader setifempty X-B3-TraceId "expr=%{md5:%{reqenv:UNIQUE_ID}}"
+RequestHeader edit X-B3-TraceId "^(.{0,16}).*$" "$1"
+```
+
+>%{reqenv:UNIQUE_ID} is a unique string generated by mod_unique_id. Then, it gets MD5-hashed and assigned to the X-B3-TraceId header. This gives a 32-character hex string = 128 bit traceId. Since my downstream libraries require the traceIds to be 64-bit, the RequestHeader edit extracts the first 16 characters (64 bit) from the value and reassigns it back to the X-B3-TraceId header which is sent downstream.