• gzip support for *.js from design elements doesn't work

    By nico Prenzel 2 decades ago

    Hello Michael,



    first thank you for that wonderfull application.



    You gzip implementation sound very interesting for me as a domino developer, so I wanted to test it.

    Because I've only one DomBulletin on my server it would'nt make sense to swap the .js to my file system and too I don't like the file system option, because I'll never remind that.



    So, I tried your V.1.1a wich introduced gzip support from design elements. Am I correct?

    I've activated the option "Enable HTTP compression". Also I've set the HTTP rules to your sample. But nothing happend. I'am hoping to see the compressed javascript gzip in the HTML source code from my broser (Opera6/IE6), but that didn't happen.

    I've also tried to setup the DomBulletin database into the HTTP rules as requested path (/DomBulletin/DomBulletin.nsf/
    .js), but also there wasn't the estaminated result.



    What am I doing wrong?



    Thanks.



    NicoP.

    • Hum...

      By Michael Bourak 2 decades ago

      how are you seeing it does not work ? The gzip feature is pretty "not visible" for end user except if you use some kind of http sniffer to see if yuo receive some gzip content.



      In domB, only part of traffic is compressed (the static part, ie libraries).



      But there may be a bug so best way would be to ping me via aim/yahoo : mbourak so we can see this together





      Btw, on www.hinkyminky.net, I use gzip option and it works…so… :)

      • Difference between yours and mine page

        By nico Prenzel 2 decades ago

        Hello,



        if I check the source code, I always get the "non-zipped" libraries (here "common.js"):

        (http://prenzel.dyndns.org/Anwendungen/Internet/Bulletin/DominoBulletin.nsf)











        Dominobulletin