Discoverer Servlet with Web Cache gzip Compression

Hi,
we have some Discoverer Worksheets which we want to access by ISDN dial in (64 kbit/sec). To speed up the response time when users use this slow connection, we want to activate Web Cache gzip compression.
But even when we enable Web Cache for Discoverer (configuration.xml), Web Cache don't compress pages generated by Discoverer Viewer. We found out that the generated responses contain the "content-disposition" HTTP-Header entry. Are we correct that this is the reason why there is no gzip compression? AND DOES ANYONE KNOW A WORKAROUND???
Best regards,
Matthias Scherer

When you set the caching rules, you can also specify whether or not you want the pages to be compressed. Web Cache compresses html pages and relies on the accept-encoding: gzip from the client header to determine whether or not to send the content compressed.

Similar Messages

  • Is it possible to enable Web Cache gzip compression with 9iAS Disco Viewer?

    Hi,
    Sorry for repeating this question. But it's very urgent and we don't have any idea yet how to solve / work around it:
    To keep it short: Is it possible to use Web Cache gzip compression for pages rendered by 9iAS Discoverer Viewer???
    Our scenario: We have some Discoverer Worksheets which we want to access by ISDN dial in (64 kbit/sec). An average page needs 2 minutes only for sending the html/javascript output rendered by Disco Viewer to the client browser.
    To speed up the response time when users use this slow connection, we want to activate Web Cache gzip compression.
    The problem: But even when we enable Web Cache for Discoverer (configuration.xml and Web Cache rules), Web Cache doesn't compress pages generated by Discoverer Viewer. We found out that the generated responses contain the "content-disposition" HTTP-Header entry. Are we correct that this is the reason why there is no gzip compression? AND DOES ANYONE KNOW A WORKAROUND (p.e. configure Disco not to add the content-disposition http header)???
    Best regards,
    Matthias Scherer

    When you set the caching rules, you can also specify whether or not you want the pages to be compressed. Web Cache compresses html pages and relies on the accept-encoding: gzip from the client header to determine whether or not to send the content compressed.

  • Is it possible to enable Web Cache gzip compression for 9iAS Disco Viewer?

    Hi,
    Sorry for repeating this question. But it's very urgent and we don't have any idea yet how to solve / work around it:
    To keep it short: Is it possible to use Web Cache gzip compression for pages rendered by 9iAS Discoverer Viewer???
    Our scenario: We have some Discoverer Worksheets which we want to access by ISDN dial in (64 kbit/sec). An average page needs 2 minutes only for sending the html/javascript output rendered by Disco Viewer to the client browser.
    To speed up the response time when users use this slow connection, we want to activate Web Cache gzip compression.
    The problem: But even when we enable Web Cache for Discoverer (configuration.xml and Web Cache rules), Web Cache doesn't compress pages generated by Discoverer Viewer. We found out that the generated responses contain the "content-disposition" HTTP-Header entry. Are we correct that this is the reason why there is no gzip compression? AND DOES ANYONE KNOW A WORKAROUND (p.e. configure Disco not to add the content-disposition http header)???
    Best regards,
    Matthias Scherer

    Matthias,
    Have you raised this as a TAR with Oracle Support? If you've got a specific question, and you need a definitive answer, raising a TAR is the best way to proceed.
    regards
    Mark Rittman

  • BI Publisher not working with Web Cache

    BI Publisher not working with Web Cache
    I'm trying to enable BI Publisher to run from the internet. I have Web Cache (AS10g rel 2) in an internet DMZ, trying to work with BI Publisher running on a AS10g rel 3 server in a application DMZ. BI Publisher won't allow Web Cache to hide the URL after login. It tries to use the application server name as a URL and gets lost, since this is not resolvable from the internet. We have Content DB, other J2EE application installed in this same configuration, and it works fine.
    This is duty managed as of today. They required an enhancement request, which I submitted. SR 6696835.993 -

    Currently an enhancement - it was logged as that but IMHO its a bug as other Oracle products work OK - it kinda depends on whether its an ORacle strd to work with webcache or not. Suffice to say, we are investigating the issue and will update the er/bug soon.
    Tim

  • Load Balancing Forms and Reports with Web Cache

    We are planning to add a second OracleAS 10g middle-tier application server to an existing 10g middle-tier.
    Both middle tiers will provide Forms and Reports.
    Users must pass through two static HTML pages before starting Forms.
    We plan to use Web Cache to load-balance (probably using round-robin) between the two middle-tiers.
    Does anyone see any problems with this solution?
    All comments/suggestions welcome.
    Thanks,
    Jim

    You could also load balance the two OC4J's using standard servlet mechanisms. I know that there exists a couple of good notes on Metalink. Go and do a search.
    Regards,
    Martin Malmstrom

  • FRM-92101: Load Balancing Forms 10g with Web Cache

    Hi,
    I´m having some problems with Oracle Forms and Webcache 10g and I was wondering if you
    could help.
    Machines: (Pentium IV 2.6 GHz; 2GB RAM; 80GB HD)
    A. Red Hat Linux AS 2.1
    Oracle AS 10g - Infrastructure Installation
    B. Windows 2000 Server - Service Pack 4
    Oracle AS 10g - BI and Forms Installation (Using Infrastructure on machine A)
    C. Windows 2000 Server - Service Pack 4
    Oracle AS 10g - BI and Forms Installation (Using Infrastructure on machine A)
    I didn´t apply any Patchsets of Oracle AS 10g. My current version is 9.0.4.0 .
    Goal:
    Use Oracle Webcache 10g on machine B for Load Balancing an Oracle Forms Application
    on machines B and C.
    Facts:
    The Oracle AS 10g installation on the 3 machines was made without problems.
    The Forms Applications are running without problems on both Forms servers in machine B and C.
    Symptoms:
    I´m getting the following error when I try to acces the forms application through Webcache:
    FRM-92101: There was a failure in the forms server during startup.
    This could happen due to invalid configuration.
    Please look in the web-server log file for details.
    But, this error happens ONLY when BOTH OC4J_BI_Forms instances (machines B and C) are
    running.
    When just one of the OC4J_BI_Forms is running everything works fine.
    Webcache Configuration:
    I´ve followed Metalink note 207668.1: Configuring Web Cache as a Load Balancer for Application Servers
    step by step to make the configuration of the following components:
    1. Configuration of the origin servers
    2. Configuration of Site definitions
    3. Configuration of Site to server mapping
    After that, I´ve follwed the Metalink note 229900.1: Integrating and using Web Cache with Forms 9i for Load Balancing
    step by step to make the configuration of the following components:
    4. Session Binding
    Then I try to test the Load Balancing and I got the error FRM-92101 when both OC4J_BI_Forms
    instance were running.
    I´ve searched Metalink and found note 268830.1: Webcache Won't Load Balance 2 Forms Instances.
    Following the note instructions I did the following changes:
    Added these lines at the end of HTTPD.conf (machine B):
    CookieTracking On
    CookieName myformscookie1
    Added these lines at the end of HTTPD.conf (machine C):
    CookieTracking On
    CookieName myformscookie2
    In Webcache configuration:
    I´ve Changed the default session binding from JSESSIONID to "ANY SET COOKIE" for the
    site's session binding.
    But even after these changes I´m getting FRM-92101 error on the same conditions.
    How can I solve this problem ?
    Thank you in advance.
    Marcus Santos.
    ([email protected])

    Just ran into this problem last Tuesday, Nov.30 and applied the changes today.
    My configuration is similar to yours: 9.0.4 web cache on machine A, 9.0.4 10gAS forms and reports standalone on machine B and C (not a cluster, no infra).
    I appended the Cookie lines you mentioned in httpd.conf located in $ORACLE_HOME/Apache/Apache/conf in both machines B and C.
    One important thing you may have missed. After changing httpd.conf in each 9iAS instance, you need to make the change known to dcmctl so issue:
    dcmctl updateConfig -ct ohs
    Then do the following for each 9iAS instance and it should be ready for webcache:
    dcmctl stop
    dcmctl start
    Setup Any-set-Cookie in webcache instead of JSESSIONID and the whole thing should now work. You can run a form through machine A which will load balance to either machine B or C (which can both be up). Then, try shutting down 9iAS on machine B or C and run a form again. They now all work.
    HTH,
    Raffy

  • Portal works bad with Web Cache

    I'm creating a web page using the Portal. I add new items to the page in the Layout view, but I can't see this new items in the Graphical view or in the View page. To my surprise this pages are cached in the Web Cache even I haven't create any rule for them, they appear as cached but without using any rule. Any idea?
    thanks.

    The following doc. might help you in how portal uses webcache for caching.
    http://portalstudio.oracle.com/pls/ops/docs/FOLDER/COMMUNITY/OTN_CONTENT/MAINPAGE/OWCOPENHAGEN/30753_FINAL.PDF
    The following doc. will help you with the Config. of the WebCache with the Portal
    http://portalcenter.oracle.com/pls/ops/docs/FOLDER/COMMUNITY/CONFIGHTML/toc.htm
    - Senthil

  • Web Cache 10g Strange Port Redirection

    Hi,
    I have installed Oracle AS 10g 10.1.2 at one server (Solaris 9).
    1) Oracle Apache Server is listenning port 81 and specific IP. No apache virtual hosts are configured at this port. In httpd.conf i have these directives:
    Port 81
    Listen xxx.xxx.xxx.xxx:81
    2) Web Cache is listenning port 80 and the same IP as Apache Server.
    3) In Web Cache, I've added one origin server with 81 port and HTTP protocol (host and port of Apache server, from item 1).
    4) Сreated new named site at port 80, which was mapped to Origin server created item 2.
    My application is deployed to url /myapp, and after configuring Web Cache as described, I could access it by typing:
    http://<host>/myapp
    But when click to any link in my app, my browser is redirected to URL with specific port
    http://<host>:81/myapp
    Where :81 is Apache Server port from "Port" directive in httpd.conf. If I change "Port" directive to different value, for example 80, browser is redirected to http://<host>:0/myapp
    Could, you help me? I need no port in my URL at all (port 80 for HTTP and 443 for HTTPS).

    Hi
    I have one named sites definitions, it is also default named site.
    Host name is <My Host>
    Port is 80 (It is that port, which WEB cache is listening)
    Prefix field is empty.
    Origin server is <My host>:81 (Actually it is my apache virtual host)
    As I've written all navigation in my application is performed over one servlet, which recieves request by method post, and uses sendRedirect method to redirect user reuqests (sending http header to browser):
    response.sendRedirect(url);
    If I change code, and servlet uses server side redirection request.getRequestDispatcher(url).forward(request, response);
    App is redirected to WEB Cache (Named Site) port. All navigation works fine with WEB Cache or without it.
    But this method doesn't suites for my application. Because if user press refresh button, browser asks to repost the data.
    Best Regards
    Nikolajs Sulima
    Message was edited by:
    [email protected]

  • IE browser and Web Cache and SSL - Internet Explorer cannot display the web page

    When using IE8, IE9, or IE10 with Web Cache and SSL certain pages which display a lot of data returns the error - "Internet Explorer cannot display the web page."
    if we eliminate SSL but continue to use Web Cache, the error does *not* reproduce & If we eliminate Web Cache altogether the error again does *not* reproduce.  The error is only reproducible when we use SSL with Web Cache and if we use IE and we access *large* pages. The error is not reproducible with Firefox or Chrome. This is a Web Tier 11.1.1.7 installation with WebLogic 10.3.6 & Red Hat Enterprise 5 Linux x86-64
    Event_log shows below errors.
    [2013-06-13T16:34:35-04:00] [webcache] [NOTIFICATION:1] [WXE-09002] [logging] [ecid: ] Generated by Oracle Web Cache on Thu Jun 13 16:34:35 2013 - Build 11.1.1.7.0 130113.0721
    [2013-06-13T16:34:36-04:00] [webcache] [NOTIFICATION:1] [WXE-08513] [logging] [ecid: ] Cache server process ID 4469 is starting up.
    [2013-06-13T16:34:36-04:00] [webcache] [NOTIFICATION:1] [WXE-09612] [main] [ecid: ] Oracle Web Cache 11g (11.1.1.6), Build 11.1.1.7.0 130113.0721
    [2013-06-13T16:34:37-04:00] [webcache] [NOTIFICATION:1] [WXE-13002] [config] [ecid: ] Maximum allowed incoming connections are 1000
    [2013-06-13T16:35:00-04:00] [webcache] [NOTIFICATION:1] [WXE-09441] [stats] [ecid: ] DMS enabled
    [2013-06-13T16:35:28-04:00] [webcache] [NOTIFICATION:1] [WXE-12209] [cluster] [ecid: ] A 1 node cluster successfully initialized
    [2013-06-13T16:35:29-04:00] [webcache] [NOTIFICATION:1] [WXE-09614] [main] [ecid: ] The following Oracle Web Cache internal files are pre-populated to the cache: [[
            /nssb-p.adm.fit.edu:7785/_oracle_http_server_webcache_static_.html
            /nssb-p.adm.fit.edu:4448/_oracle_http_server_webcache_static_.html
    [2013-06-13T16:35:29-04:00] [webcache] [NOTIFICATION:1] [WXE-09614] [main] [ecid: ]  [[
    The following Oracle Web Cache internal files are pre-populated to the cache: [[
            /nssb-p.adm.fit.edu:7785/_oracle_http_server_webcache_checkserviceavailability_.html
            /nssb-p.adm.fit.edu:4448/_oracle_http_server_webcache_checkserviceavailability_.html
    [2013-06-13T16:35:29-04:00] [webcache] [NOTIFICATION:1] [WXE-09608] [main] [ecid: ] The cache server process started successfully.
    [2013-06-13T16:35:29-04:00] [webcache] [WARNING:1] [WXE-12104] [utl] [ecid: ] Oracle Web Cache process has page faulted
    [2013-06-13T16:44:22-04:00] [webcache] [ERROR:32] [WXE-11904] [security] [ecid: ] SSL handshake fails SSL-29049
    [2013-06-13T16:44:22-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: The record type is unknown.
    [2013-06-13T16:44:22-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: Remote IP [163.118.22.16]:55145
    [2013-06-13T16:44:22-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: Local IP 163.118.170.70:4448
    [2013-06-13T16:44:22-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: SSL error during handshake (details: internal=The record type is unknown. system=Success)
    [2013-06-13T16:44:27-04:00] [webcache] [ERROR:32] [WXE-11904] [security] [ecid: ] SSL handshake fails SSL-29049
    [2013-06-13T16:44:27-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: The record type is unknown.
    [2013-06-13T16:44:27-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: Remote IP [163.118.22.16]:55144
    [2013-06-13T16:44:27-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: Local IP 163.118.170.70:4448
    [2013-06-13T16:44:27-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: SSL error during handshake (details: internal=The record type is unknown. system=Success)
    [2013-06-13T16:44:27-04:00] [webcache] [ERROR:32] [WXE-11904] [security] [ecid: ] SSL handshake fails SSL-29049
    [2013-06-13T16:44:27-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: The record type is unknown.
    [2013-06-13T16:44:27-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: Remote IP [163.118.22.16]:55148
    [2013-06-13T16:44:27-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: Local IP 163.118.170.70:4448
    [2013-06-13T16:44:27-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: SSL error during handshake (details: internal=The record type is unknown. system=Success)
    [2013-06-13T16:44:35-04:00] [webcache] [ERROR:32] [WXE-11904] [security] [ecid: ] SSL handshake fails SSL-28864
    [2013-06-13T16:44:35-04:00] [webcache] [ERROR:32] [WXE-11904] [security] [ecid: ] SSL handshake fails SSL-28864
    [2013-06-13T16:44:47-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: This error occurred because the peer closed the connection.
    [2013-06-13T16:44:47-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: success during initialization (details: internal=success system=Success)
    [2013-06-13T16:44:47-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: This error occurred because the peer closed the connection.
    [2013-06-13T16:44:47-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: success during initialization (details: internal=success system=Success)
    [2013-06-13T16:44:47-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: This error occurred because the peer closed the connection.
    [2013-06-13T16:44:47-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: success during initialization (details: internal=success system=Success)
    [2013-06-13T16:44:47-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: This error occurred because the peer closed the connection.
    [2013-06-13T16:44:47-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: success during initialization (details: internal=success system=Success)
    [2013-06-13T16:44:47-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: This error occurred because the peer closed the connection.
    [2013-06-13T16:44:47-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: success during initialization (details: internal=success system=Success)
    [2013-06-13T16:44:47-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: This error occurred because the peer closed the connection.
    [2013-06-13T16:44:47-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: success during initialization (details: internal=success system=Success)
    [2013-06-13T16:45:18-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: This error occurred because the peer closed the connection.
    [2013-06-13T16:45:18-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: success during initialization (details: internal=success system=Success)
    [2013-06-13T16:45:22-04:00] [webcache] [ERROR:32] [WXE-11904] [security] [ecid: ] SSL handshake fails SSL-28864
    [2013-06-13T16:45:22-04:00] [webcache] [ERROR:32] [WXE-11904] [security] [ecid: ] SSL handshake fails SSL-28864
    [2013-06-13T16:45:38-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: This error occurred because the peer closed the connection.
    [2013-06-13T16:45:38-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: success during initialization (details: internal=success system=Success)
    [2013-06-13T16:45:38-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: This error occurred because the peer closed the connection.
    [2013-06-13T16:45:38-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: success during initialization (details: internal=success system=Success)
    [2013-06-13T16:45:38-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: This error occurred because the peer closed the connection.
    [2013-06-13T16:45:38-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: success during initialization (details: internal=success system=Success)
    [2013-06-13T16:45:38-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: This error occurred because the peer closed the connection.
    [2013-06-13T16:45:38-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: success during initialization (details: internal=success system=Success)
    [2013-06-13T16:45:41-04:00] [webcache] [WARNING:1] [WXE-11905] [security] [ecid: ] SSL additional information: This error occurred because the peer closed the connection.
    [2013-06-13T16:45:41-04:00] [webcache] [WARNING:1] [WXE-11906] [security] [ecid: ] SSL details: success during initialization (details: internal=success system=Success)
    Any help or suggestions are greatly appreciated
    Tnx a lot,
    Lokesh

    Hello ,
    Try Below Workarounds:
    Workaround 1:
    Open Central Admin
    àApplication Management  à
    Configure Alternate access mapping-->Edit your web application zone and add your server name in Intranet zone. So default can be serverIP and intranet could be servername.
    Workaround 2:
    Might be there is some issue with DNS and try to check that WebApplication is pointing to correct IP or not.  
    Also try to access your Sharepoint site using ip Address .. If you still gets error Kindly share the logs .. 
    Best
    Regards Kuldeep Verma
    Please remember to click "Mark As Answer"
    if a post solves your problem or "Vote As Helpful" if it was useful.

  • Configure Web Cache in a DMZ

    hI,
    I try to configure a linux machine with Web cache and Apache. My ideia is, when some users try to come to company internal site the web cache redirect the request for the internal site by 80 port.
    The apache by default listen in port 7780. I try to add port 80 but in EVENT_LOG file I receive the following error:
    "failed to assign port 80, bind() error = permission denied".
    Can anyone help me?
    Thanks,
    Carlos

    Thanks.
    I already do that and already create a virtual host....
    My problem is the following:
    I have one Oracle Applications with this URL, http://hostname:7779/pls/aplication and my ideia is when you type http://www.client.pt in DMZ you go direct to the http://name:7779/pls/aplication (login page).
    I already configured the http://www.client.pt for http://hostname:7778.
    Thanks,
    Carlos

  • Some confusion about Web Cache clustering for load balancing

    I have 4 Windows 2003 identical machines having OAS 10g installed with Web Cache (Same Passwords and Oracle Home) . I want to utilize them for load-balancing using Microsoft Network Load-balancing. I followed the Note: 259208.1 till step#10. Now we have virtual machine "IASPROD" for all other nodes {IASPROD1,IASPROD2,IASPROD3,IASPROD4 } I am able to logon to Web Cache manager from all nodes separately.
    On Node-1 I added all nodes entries in " Origin Server " having routed "Enabled " for all of them. Same I did added in Site-Definitions and gave alias hostname as "IASPROD" which is virtual server.
    Priority =1
    Site Hostname =iasprod1.domain Port = 80
    Policy = Unrestricted
    Origin Server Hostnames , port,proxy
    iasprod1.domain 7778 No
    iasprod2.domain 7778 No
    iasprod3.domain 7778 No
    iasprod4.domain 7778 No
    I have couple of questions might be very basic but as I am configuring very first time.
    1. How do I access all the machines through virtual name as stated above ? I tried but not working.
    2. This cluster setup should be repeated for all Nodes or for only node-1.
    3. If for only Node-1 than what will heppen in case of Node-1 goes down.
    4. How can I verify Load-balancing is working ?
    If you guyz can guide me than I'll be very greatful.

    One more addition Database is on AIX (9.2.0.4)

  • Can Web Cache rewrite HTTP_REFERER headers?

    Can Web Cache be configured to rewrite the HTTP_REFERER header to replace the Web Cache site address:port with the dispatched application server address:port?
    i.e.
    If there is a Web Cache site listening on webcache.domain:80 and it is mapped to application servers: appserver1.domain:7778 and appserver2.domain:7778.
    And a user requests page webcache.domain/page1, which contains a link to page2.
    And then the user opens the link to page2, and Web Cache decides to send the request on to appserver2.
    Can Web Cache be configured to change the HTTP_REFERER header from webcache.domain/page1 to appserver2.domain/page1?
    This is important to our application, because we want to verify that our processing pages are invoked from our application validation pages (we know this method is not 100% tamper proof).
    We would prefer to not have to change our application code to support Web Cache
    Thanks for any info or suggestions, -Steve

    Thanks Jean
    I've added comments to extracts from your post.
    Let's say you suddenly get a request for p2, even if
    it was from the history of the browser, it would still
    contain a referer header of p1, and is no different
    from what it would be when the user was going through
    the proper steps? Are you saying the p2 generated from
    your JavaScript will have a different referer from the
    p2 generated from browser history? If so, how are they
    differ exactly?The browser history does not include the referer. So p2 requested from the history list does not include a referer although the original link from p1 did.
    Without Web Cache, the flow is:
    Step 1: a user requests appserver/page1. page1 is added to the browser history. page1 is loaded and executes JavaScript to display page2 in an iFrame. page2 is not added to the browser history (just like style sheets and other embedded requests do not get included in the history). page2 is loaded and executes JavaScript to submit an html form to load page3 into a hidden iFrame and wait for it to load. page3 is added to the browser's history becuase it was submitted; not embedded. Assuming that the request for page1 came from the browser's history, favorites, a link from an e-mail (the usual for us), or was entered manually - there will be no referer for page1. The expected referer for page2 is appserver/page1, and the expected referer for page3 is appserver/page2.
    Step2: while processing page3, the application compares the server name in the requested URL (appserver/page3) with the server name from the referer URL (appserver/page2), if the servers match, page3 accesses the database and sends the requested data to the browser
    Step3: JavaScript in page2 detects that page3 has loaded, interprets the results from page3, updates the content displayed by page2, and returns control to the browser user
    Since this works with your app, how is webcache in
    front going to break it? Note that when passing a
    request
    to the app server, web cache does not modify the
    host header in the request.without Web Cache the browser sends requests directly to the appserver, so the request/referer entries seen by the application look like:
    appserver/page1 -
    appserver/page2 appserver/page1
    appserver/page3 appserver/page2
    with Web Cache the browser sends requests to webcache, so the request/referer entries seen by the application look like:
    appserver/page1 -
    appserver/page2 webcache/page1
    appserver/page3 webcache/page2
    This is because the Web Cache changed the request URL and did not change the referer URL.
    So request to webcache.domain/abc will be sent to your
    app server as is.I don't think so, doesn't the requested URL change as a result of the Web Cache mapping? i.e. webcache.domain/abc --> appserver.domain/abc
    And since we do not change the referer
    header, either, whatever works for your app now should
    still work for you with webcache in front. This is
    assuming you only do comparisons on the 2 hosts to see
    if they are the same. Web Cache is changing one (request URL) of the two items (request URL and referer URL) that the application server compares.
    The reason has been that we are
    a cache, and in principal should be as transparent
    as possible, so we try to stay away from app-sever/
    apache like functionality.I support that principle 100% - from the application server perspective, it should not need to differentiate between a request directly from a browser, and a request that was issued by the cache on behalf of a browser.
    The cache should completely pretend that it is the originating browser. A browser sends the request and the referer URLs. In application flow, a relationship can be inferred/required between the two URLs. Web Cache is changing one without changing the other and breaking the relationship that the application server would normally expect.
    But I'm still
    not convinced that you need that in webcache. :)If we want to use Web Cache in front of this application, without changing the application, then we need it. :)
    Of course, we could change our application, but the more I think about the principles involved, the more I believe that it is the cache that needs changing. However, I will take another look to see if there are other standard headers related to a request that are present with and without Web Cache, and that can be used to reliably compare the server in the request URL with the server in the referer URL. If there are, then I can happily change our application so that it will work with or without Web Cache.
    -Steve

  • HTTP Headers - enabling caching and compression with the portal?

    Has anyone configured their web server (IIS or Apache) or use a commercial product to flawlessly cache and compress all content generated by the portal?
    Compression and caching is critical for making our portal based applictions work for overseas users. It should be doable, just taking advantage of standard HTTP protocols, but implementing this a complex system like the portal is tricky, we seem to be generating different values in the HTTP Headers for the same types of files (such as CSS).
    We are running Apache so can't take advantage of the built in compression capabilities of the .net portal. We are running the java vervion. 6.1 mp1, sql server 2000 (portal, search, collab, publisher, studio, analytics, custom .net and java portlets on remote server).
    Basically our strategy is to compress all outgoing static and dynamic text content (html, CSS, javascript), and to cache all static files (CSS, javascript, images) for 6 months to a year depending on file type.
    Here are some links on the subjects of caching and compression that I have compiled:
    Caching & Compression info and tools
    http://www.webreference.com/internet/software/servers/http/compression/
    http://www.ibm.com/developerworks/web/library/wa-httpcomp/
    http://www.mnot.net/cache_docs/
    http://www.codeproject.com/aspnet/HttpCompressionQnD.asp?df=100&forumid=322472&exp=0&select=1722189#xx1722189xx
    http://en.wikipedia.org/wiki/Http_compression
    http://perl.apache.org/docs/tutorials/client/compression/compression.html
    https://secure.xcache.com/Page.aspx?c=60&p=590
    http://www.codinghorror.com/blog/archives/000807.html
    http://www.howtoforge.com/apache2_mod_deflate
    http://www.ircache.net/cgi-bin/cacheability.py
    http://betterexplained.com/articles/how-to-optimize-your-site-with-http-caching/
    http://betterexplained.com/articles/speed-up-your-javascript-load-time/
    http://betterexplained.com/articles/speed-up-your-javascript-load-time/
    http://www.rubyrobot.org/article/5-tips-for-faster-loading-web-sites
    http://betterexplained.com/articles/how-to-optimize-your-site-with-gzip-compression/
    http://www.gidnetwork.com/tools/gzip-test.php
    http://www.pipeboost.com/
    http://www.schroepl.net/cgi-bin/http_trace.pl
    http://leknor.com/code/gziped.php?url=http%3A%2F%2Fwww.google.com
    http://www.port80software.com/surveys/top1000compression/
    http://www.rexswain.com/httpview.html
    http://www.15seconds.com/issue/020314.htm
    http://www.devwebpro.com/devwebpro-39-20041117DevelopingYourSiteforPerformanceCompressionandOtherServerSideEnhancements.html
    http://www.webpronews.com/topnews/2004/11/17/developing-your-site-for-performance-optimal-cache-control
    http://www.sitepoint.com/print/effective-website-acceleration
    http://nazish.blog.com/1007523/
    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/IETechCol/dnwebgen/IE_Fiddler2.asp?frame=true
    http://www.fiddlertool.com/fiddler/version.asp
    http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html
    http://www.web-caching.com/cacheability.html
    http://www.edginet.org/techie/website/http.html
    http://www.cmlenz.net/blog/2005/05/on_http_lastmod.html
    http://www.websiteoptimization.com/speed/tweak/cache/
    http://www.webperformance.org/caching//caching_for_performance.html
    http://betterexplained.com/articles/how-to-debug-web-applications-with-firefox/
    Edited by tkoenings at 06/18/2007 6:26 AM

    Hi Scott,
    Does Weblogic platform 8.1 supports netscape? We have developed a portal which
    works perfectly on IE but it dies in netscape. Is netUI tags not supported in
    Netscape?
    Pls reply
    manju
    Scott Dunbar <[email protected]> wrote:
    From a pure HTML perspective Portal does it's rendering with nested
    tables.
    Netscape 4.x and below have terrible performance with nested tables.
    The
    problem is not the Portal server but rather Netscape on the client machine.
    If IE and/or a recent version of Netscape/Mozilla is not possible then
    there are
    really only two options:
    1) Faster client hardware - not likely to be an acceptable solution.
    2) Minimize the number of portlets and the complexity within the portlets.
    Neither of these solutions are a great answer, but the 4.7 series of
    Netscape is
    getting pretty old. Having said that, we've got customers who want to
    continue
    to use IE 4 :)
    Again, though, this problem is, I'm afraid out of our hands. It is the
    client
    rendering time that is the issue.
    cg wrote:
    Does anyone know of any known reasons why the 7.0 (did it also with4.0) portal
    pages can take up to almost 30 seconds to load in Netscape 4.7? I knowit is a
    very generic question but our customer still uses 4.7 and will notuse the portal
    b/c it takes so long to load some of the webapps. What the pages willdo when
    loading is that the headers will come up and when it gets to the bodyof the page
    it seems to stall and then comes up all of a sudden. For some of thepages it
    takes 6 seconds and for others it takes about 24-27 seconds.
    We have suggested using IE only but that is not an option with allof the customers
    and getting a newer version of Netscape is also out of the question.
    Any suggestions would be greatly appreciated.--
    scott dunbar
    bea systems, inc.
    boulder, co, usa

  • HTTP Cache control / GZIP compression

    Hi,
    is it possible to add / enable cache control / compression in Connect Pro (7 or 8)? If so, how?
    I suspect we'll have to tweak the underlying http server for it but I'd like to know if this is documented somewhere and if it's supported. Especially, we'd like to
    - add / configure Cache-Control http headers
    - add / configure Expires http headers
    - activate GZIP/Deflate compression
    If this isn't something Connect offers out of the box, any recommendations for proxy servers to put in front of Connect and things to watch out for?
    Thanks,
    Dirk.

    Thanks. We solved it by adding a custom Servlet Filter to the web.xml.
    Dirk.

  • ADF application integrating with Oracle Web Cache

    Hello,
    I am trying to integrated my ADF 11g application with Oracle Web Cache. I used this link http://andrejusb.blogspot.com/2010/06/oracle-webtier-11g-configuration-for.html for it.
    I am able to access my ADF application using webcache port 7785.
    I created few caching rules in the Oracle Web Cache. And in the popular request section of the Oracle Web cache i see jpg,png and other image files cached.
    But the issue is when the application access images like /testapp/test/images/abc.jpg?_adf.ctrl-state=5b0s7lzfo_29 . I created a caching rule with regular expression ^/testapp/test/images/[A-Za-z0-9_]*\.(gif|jpeg|png|jpg)\?_adf\.ctrl-state=[A-Za-z0-9_]*$.
    But when i access the popular request in em i don't see the URL given above as cached. The caching reason it specifies as URL contains query string.
    I am not sure if i need to do anything additional to cache these URL's as well.
    Thanks!
    Ram

    Yes that works. But my question is how to cache the urls which has querystring. I was trying to give a regular expression to match the url so that the url which contains parameters like _afrLoop which changes with each HTTP request can also be cached.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

Maybe you are looking for