# HTTP encoding

**URL:** <https://community.zeek.org/t/http-encoding/948>\
**Category:** Zeek\
**Created:** [April 3, 2006, 11:06pm UTC](https://community.zeek.org/t/http-encoding/948 "2006-04-03T23:06:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vern](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/vern/32/630_2.png) [@Vern](https://community.zeek.org/u/Vern)\
**Post date:** [April 3, 2006, 11:06pm UTC](https://community.zeek.org/t/http-encoding/948/1 "2006-04-03T23:06:38Z")

</div>

> I was testing some evasion techniques using HTTP unicode encoding, and I was  
> surprised to see that Bro seems to completely miss the attacks in that case.

Indeed, it lacks a Unicode decoder :-(. Morley Mao wrote one a while ago,  
which unfortunately never got integrated. I'd be happy to send it along  
to someone who wants to bring it up to date (and I promise to integrate  
the result!).

&nbsp;&nbsp;&nbsp;&nbsp;Vern

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex011/uploads/zeek/original/1X/f09d732bc2cc7c7cc7e35db67cf4e1d5233ce7a7.png) [@system](https://community.zeek.org/u/system)\
**Post date:** [May 6, 2022, 3:37pm UTC](https://community.zeek.org/t/http-encoding/948/2 "2022-05-06T15:37:50Z")

</div>


