Hi Yang,

'\0x09' is the same with '\t' , they get the same byte value 9.  '\0x09'
and '\t' are just different human readable format display.

So for java "*Wind ows NT*".equals("*Wind\tows NT*") .

By the way nginx-clojure won't do any converting about this case it just
keep the original value.


Here 's my test about print headers to client :

$ curl -H "User-Agent:Windows        NT" http://localhost:8080/prheaders

the server reply :

{host localhost:8080, accept */*, user-agent Windows NT}



Xfeep

On Tue, Sep 16, 2014 at 10:14 AM, 扬清风 <sfw2005...@gmail.com> wrote:

> Hi xfeep,
>
> How do the nginx_clojure do with special char(even bytes not printable) in
> http message? For example,
>
> Accept: image/png, image/svg+xml, image/*;q=0.8, */*;q=0.5
> Referer: http://www.cyclingnews.com/
> Accept-Language: zh-CN
> User-Agent: Mozilla/5.0 (Wind    ows NT 6.1; WOW64; Trident/7.0; rv:11.0)
> like Gecko
> Accept-Encoding: gzip, deflate
>
> For "User-Agent" item, I put a tab in the "Wind    ows". In this case,
> original Nginx would escapse to "Windo\x09ws NT" in accesss log. But when I
> fetch this header from Nginx_clojure java handler, the value come to be
> "Wind\tows NT". Is there any configuration in Nginx_clojure for this if I
> expect to get escapse value "\x09" for "tab" instead of "\t"?
>
> Thank you very much !!!
> Robert.Yang
>
>
> On Sunday, September 7, 2014 8:45:59 PM UTC+8, xfeep wrote:
>>
>> 0.2.5 (2014-09-07)
>>
>>    1. New Feature: Reference variables in jvm_options & different jvm
>>    debug ports for jvm processes (issue #42)
>>    2. New Feature: Server Sent Events(SSE) & Long polling (issue #41,
>>    issue #36)
>>    3. New Feature: Supports 64-bit JDK on 64-bit Windows (issue #40)
>>    4. New Feature: Coroutine based socket supports JDK8 (issue #39)
>>    5. New Feature: More easier to archive Sub/Pub services with
>>    Broadcast Events to all Nginx workers (issue #39)
>>    6. New Feature: Asynchronous Channel a wrapper of asynchronous socket
>>    to make the usage easier (issue #37)
>>    7. Enhancement: Fix--On Windows a little many write events happen and
>>    these events seem useless (issue #35)
>>
>>
>> So far Nginx-Clojure have supported:
>>
>>
>>    - Linux x86 32-bit (tested with CentOS 5.10 i386 )
>>    - Linux x64 (tested with CentOS 5.10 x64, Ubuntu  13.10 x64, Alpine
>>    Linux 3.03 x64)
>>    - Windowns x86 32-bit (tested with Windows XP 32-bit)
>>    - Windows X64 (tested with Windows XP 64-bit)
>>    - MacOSX  (tested with MacOSX 10.7 X64)
>>
>>
>> Web Site   http://nginx-clojure.github.io/
>> Source Hosted on Github https://github.com/nginx-clojure/nginx-clojure
>> Google Group (mailing list) https://groups.google.
>> com/forum/#!forum/nginx-clojure
>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Nginx-Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to nginx-clojure+unsubscr...@googlegroups.com.
> To post to this group, send email to nginx-cloj...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/nginx-clojure/dfe85140-c92b-429c-a060-29bcff425215%40googlegroups.com
> <https://groups.google.com/d/msgid/nginx-clojure/dfe85140-c92b-429c-a060-29bcff425215%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to