<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: CSM redirect - header length in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/csm-redirect-header-length/m-p/966583#M18982</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I upgraded our CSM in our lab environment with 4.2.9. This did not fix the problem. It still appears that the url can be cut down to around 1850 bytes and the CSM will reply with the redirect. But the one that is posted here shows up to be 2277 bytes and it never gets a redirect. I am currently waiting on our TCOM guys (I am a web guy) to get their sniffer set up so I can get a capture file. Hope to post this up this afternoon. Thanks for all of your suggestions and help so far.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 22 May 2008 16:49:26 GMT</pubDate>
    <dc:creator>aanelso1</dc:creator>
    <dc:date>2008-05-22T16:49:26Z</dc:date>
    <item>
      <title>CSM redirect - header length</title>
      <link>https://community.cisco.com/t5/application-networking/csm-redirect-header-length/m-p/966575#M18974</link>
      <description>&lt;P&gt;We have a set of vservers on a CSM running 4.2.5. The TCP port 80 rule sends the request to a serverfarm with a vserver-redirect to force the request to use TCP port 443. There is a second vserver for TCP port 443 that accepts the redirect and forwards to the SSL module.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem is that when an extra long url is sent the CSM never replies from the request to TCP port 80 (we see the syn, syn-ack, ack, then several tries from the client using the GET verb (all others are TCP restransmissions - no ACKs from the CSM or server).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If we send the same request directly to the vserver on TCP port 443 it works fine. Can you give us insight as to what we might be able to do? Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Fri, 16 May 2008 15:13:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/csm-redirect-header-length/m-p/966575#M18974</guid>
      <dc:creator>aanelso1</dc:creator>
      <dc:date>2008-05-16T15:13:30Z</dc:date>
    </item>
    <item>
      <title>Re: CSM redirect - header length</title>
      <link>https://community.cisco.com/t5/application-networking/csm-redirect-header-length/m-p/966576#M18975</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;http parse length problem.&lt;/P&gt;&lt;P&gt;Increase it with the command :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;gdufour-cat6k-2(config-slb-vserver)#parse-length ?&lt;/P&gt;&lt;P&gt;  &amp;lt;1-4000&amp;gt;        maximum number of bytes to parse&lt;/P&gt;&lt;P&gt;  default-policy  set default policy when maximum parse length is reached for a&lt;/P&gt;&lt;P&gt;                  session&lt;/P&gt;&lt;P&gt;  &lt;CR&gt;&lt;/CR&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 May 2008 17:07:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/csm-redirect-header-length/m-p/966576#M18975</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2008-05-16T17:07:43Z</dc:date>
    </item>
    <item>
      <title>Re: CSM redirect - header length</title>
      <link>https://community.cisco.com/t5/application-networking/csm-redirect-header-length/m-p/966577#M18976</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for your quick reply!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I looked at the request with an HTTP sniffer and see that it is 2277 bytes. I changed the vserver that is its destination using the parse-length command to 4000 bytes (max), but it is still hanging. I will do some more testing, but is it possible that maybe the redirect serverfarm is having the problem? I never see the 302 redirect take place with this length of request, however shorter requests work fine. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 May 2008 17:43:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/csm-redirect-header-length/m-p/966577#M18976</guid>
      <dc:creator>aanelso1</dc:creator>
      <dc:date>2008-05-16T17:43:31Z</dc:date>
    </item>
    <item>
      <title>Re: CSM redirect - header length</title>
      <link>https://community.cisco.com/t5/application-networking/csm-redirect-header-length/m-p/966578#M18977</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;gdufour-cat6k-2#sho mod csm 3 tech proc 4 | i parse&lt;/P&gt;&lt;P&gt;        LB Rjct: L7 max parse len                      0&lt;/P&gt;&lt;P&gt;        LB Rjct: L7 parser                             0&lt;/P&gt;&lt;P&gt;gdufour-cat6k-2#&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If these counters are still increasing, you did not solve the problem of header length.&lt;/P&gt;&lt;P&gt;The default is 2000 bytes, so 2277 is above it and would clearly result in no response.&lt;/P&gt;&lt;P&gt;Increasing the parse length should work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 May 2008 18:41:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/csm-redirect-header-length/m-p/966578#M18977</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2008-05-16T18:41:49Z</dc:date>
    </item>
    <item>
      <title>Re: CSM redirect - header length</title>
      <link>https://community.cisco.com/t5/application-networking/csm-redirect-header-length/m-p/966579#M18978</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Must be something else...I do not see that counter incrementing. See the output below (I had my browser trying to open the url during this time). Also notice details on the vserver that is its destination. max parse len = 12000 (is this bytes or bits?).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;% Unrecognized command&lt;/P&gt;&lt;P&gt;bvldclbrtr1#sho mod csm 1 tech pro&lt;/P&gt;&lt;P&gt;bvldclbrtr1#sho mod csm 1 tech proc 4 | in&lt;/P&gt;&lt;P&gt;bvldclbrtr1#sho mod csm 1 tech proc 4 | include parse&lt;/P&gt;&lt;P&gt;        LB Rjct: L7 max parse len                      5        (5)&lt;/P&gt;&lt;P&gt;        LB Rjct: L7 parser                             0&lt;/P&gt;&lt;P&gt;bvldclbrtr1#sho mod csm 1 tech proc 4 | include parse&lt;/P&gt;&lt;P&gt;        LB Rjct: L7 max parse len                      5&lt;/P&gt;&lt;P&gt;        LB Rjct: L7 parser                             0&lt;/P&gt;&lt;P&gt;bvldclbrtr1#sho mod csm 1 tech proc 4 | include parse&lt;/P&gt;&lt;P&gt;        LB Rjct: L7 max parse len                      5&lt;/P&gt;&lt;P&gt;        LB Rjct: L7 parser                             0&lt;/P&gt;&lt;P&gt;bvldclbrtr1#sho mod csm 1 tech proc 4 | include parse&lt;/P&gt;&lt;P&gt;        LB Rjct: L7 max parse len                      5&lt;/P&gt;&lt;P&gt;        LB Rjct: L7 parser                             0&lt;/P&gt;&lt;P&gt;bvldclbrtr1#sho mod csm 1 tech proc 4 | include parse&lt;/P&gt;&lt;P&gt;        LB Rjct: L7 max parse len                      5&lt;/P&gt;&lt;P&gt;        LB Rjct: L7 parser                             0&lt;/P&gt;&lt;P&gt;bvldclbrtr1#sho mod csm 1 tech proc 4 | include parse&lt;/P&gt;&lt;P&gt;        LB Rjct: L7 max parse len                      5&lt;/P&gt;&lt;P&gt;        LB Rjct: L7 parser                             0&lt;/P&gt;&lt;P&gt;bvldclbrtr1#sho mod csm 1 tech proc 4 | include parse&lt;/P&gt;&lt;P&gt;        LB Rjct: L7 max parse len                      5&lt;/P&gt;&lt;P&gt;        LB Rjct: L7 parser                             0&lt;/P&gt;&lt;P&gt;bvldclbrtr1#sho mod csm 1 tech proc 4 | include parse&lt;/P&gt;&lt;P&gt;        LB Rjct: L7 max parse len                      5&lt;/P&gt;&lt;P&gt;        LB Rjct: L7 parser                             0&lt;/P&gt;&lt;P&gt;bvldclbrtr1#sho mod csm 1 tech proc 4 | include parse&lt;/P&gt;&lt;P&gt;        LB Rjct: L7 max parse len                      5&lt;/P&gt;&lt;P&gt;        LB Rjct: L7 parser                             0&lt;/P&gt;&lt;P&gt;bvldclbrtr1#sho mod csm 1 tech proc 4 | include parse&lt;/P&gt;&lt;P&gt;        LB Rjct: L7 max parse len                      5&lt;/P&gt;&lt;P&gt;        LB Rjct: L7 parser                             0&lt;/P&gt;&lt;P&gt;bvldclbrtr1#sho mod csm 1 tech proc 4 | include parse&lt;/P&gt;&lt;P&gt;        LB Rjct: L7 max parse len                      5&lt;/P&gt;&lt;P&gt;        LB Rjct: L7 parser                             0&lt;/P&gt;&lt;P&gt;bvldclbrtr1#sho mod csm 1 vser&lt;/P&gt;&lt;P&gt;bvldclbrtr1#sho mod csm 1 vservers name ITS-T detail&lt;/P&gt;&lt;P&gt;ITS-T, type = SLB, state = OPERATIONAL, v_index = 527&lt;/P&gt;&lt;P&gt;  virtual = 158.139.218.77/32:80 bidir, TCP, service = NONE, advertise = FALSE&lt;/P&gt;&lt;P&gt;  idle = 3600, replicate csrp = none, vlan = 218, pending = 30, layer 4&lt;/P&gt;&lt;P&gt;  max parse len = 12000, persist rebalance = TRUE&lt;/P&gt;&lt;P&gt;  ssl sticky offset = 0, length = 32&lt;/P&gt;&lt;P&gt;  conns = 0, total conns = 64&lt;/P&gt;&lt;P&gt;  Default policy:&lt;/P&gt;&lt;P&gt;    server farm = R-ITS-T, backup = &lt;NOT assigned=""&gt;&lt;/NOT&gt;&lt;/P&gt;&lt;P&gt;    sticky: timer = 0, subnet = 0.0.0.0, group id = 0&lt;/P&gt;&lt;P&gt;  Policy          Tot matches  Client pkts  Server pkts&lt;/P&gt;&lt;P&gt;  -----------------------------------------------------&lt;/P&gt;&lt;P&gt;  (default)       64           1069         871&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;bvldclbrtr1#&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 May 2008 18:55:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/csm-redirect-header-length/m-p/966579#M18978</guid>
      <dc:creator>aanelso1</dc:creator>
      <dc:date>2008-05-16T18:55:04Z</dc:date>
    </item>
    <item>
      <title>Re: CSM redirect - header length</title>
      <link>https://community.cisco.com/t5/application-networking/csm-redirect-header-length/m-p/966580#M18979</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what version do you run ?&lt;/P&gt;&lt;P&gt;Could you show the current config ?&lt;/P&gt;&lt;P&gt;Can you sniff the traffic from the CSM portchannel when connecting from the client ?&lt;/P&gt;&lt;P&gt;Is this counter increasing when you connect from the client :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(default) 64 1069 871&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 17 May 2008 12:32:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/csm-redirect-header-length/m-p/966580#M18979</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2008-05-17T12:32:02Z</dc:date>
    </item>
    <item>
      <title>Re: CSM redirect - header length</title>
      <link>https://community.cisco.com/t5/application-networking/csm-redirect-header-length/m-p/966581#M18980</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are running version 4.2.5. I will get a sniff of the traffic on port channel 257 for you. No the counter that you had me check for is not increasing when I connect as a client. Below is the current configuration:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; serverfarm R-ITS-T&lt;/P&gt;&lt;P&gt;  nat server&lt;/P&gt;&lt;P&gt;  no nat client&lt;/P&gt;&lt;P&gt;  redirect-vserver R-ITS-T&lt;/P&gt;&lt;P&gt;   webhost relocation its-t.conocophillips.net/%p&lt;/P&gt;&lt;P&gt;   ssl 443&lt;/P&gt;&lt;P&gt;   idle 120&lt;/P&gt;&lt;P&gt;   inservice&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt; vserver ITS-T&lt;/P&gt;&lt;P&gt;  virtual 10.12.120.77 tcp www&lt;/P&gt;&lt;P&gt;  vlan 218&lt;/P&gt;&lt;P&gt;  serverfarm R-ITS-T&lt;/P&gt;&lt;P&gt;  persistent rebalance&lt;/P&gt;&lt;P&gt;  parse-length 4000&lt;/P&gt;&lt;P&gt;  inservice&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt; vserver ITS-T-SSL&lt;/P&gt;&lt;P&gt;  virtual 10.12.120.77 tcp https&lt;/P&gt;&lt;P&gt;  serverfarm SSL-MODULE2&lt;/P&gt;&lt;P&gt;  persistent rebalance&lt;/P&gt;&lt;P&gt;  inservice&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt; vserver ITS-T-V4&lt;/P&gt;&lt;P&gt;  virtual 10.12.120.77 tcp www&lt;/P&gt;&lt;P&gt;  vlan 4&lt;/P&gt;&lt;P&gt;  serverfarm BVLWBIT184&lt;/P&gt;&lt;P&gt;  persistent rebalance&lt;/P&gt;&lt;P&gt;  inservice&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The url that is trying to be sent is below (which works fine if we send it to vserver ITS-T-SSL on port 443). It is on the redirect that is failing:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://its-t.conocophillips.net/sap/bc/bsp/sap/z_ext_resp/default.htm?WI=000101281590&amp;amp;OBT=ZEPAYINVST&amp;amp;OBK=2008042510064100108846WRMATHE&amp;amp;RSP=2&amp;amp;MSC=00001-00002-00003-00004-00005-00006-00007-00008-00009-00010-00011-00012-00013-00014-00015-00016-00017-00018-00019-00020-00021-00022-00023-00024-00025-00026-00027-00028-00029-00030-00031-00032-00033-00034-00035-00036-00037-00038-00039-00040-00041-00042-00043-00044-00045-00046-00047-00048-00049-00050-00051-00052-00053-00054-00055-00056-00057-00058-00059-00060-00061-00062-00063-00064-00065-00066-00067-00068-00069-00070-00071-00072-00073-00074-00075-00076-00077-00078-00079-00080-00081-00082-00083-00084-00085-00086-00087-00088-00089-00090-00091-00092-00093-00094-00095-00096-00097-00098-00099-00100-00101-00102-00103-00104-00105-00106-00107-00108-00109-00110-00111-00112-00113-00114-00115-00116-00117-00118-00119-00120-00121-00122-00123-00124-00125-00126-00127-00128-00129-00130-00131-00132-00133-00134-00135-00136-00137-00138-00139-00140-00141-00142-00143-00144-00145-00146-00147-00148-00149-00150-00151-00152-00153-00154-00155-00156-00157-00158-00159-00160-00161-00162-00163-00164-00165-00166-00167-00168-00169-00170-00171-00172-00173-00174-00175-00176-00177-00178-00179-00180-00181-00182-00183-00184-00185-00186-00187-00188-00189-00190-00191-00192-00193-00194-00195-00196-00197-00198-00199-00200-00201-00202-00203-00204-00205-00206-00207-00208-00209-00210-00211-00212-00213-00214-00215-00216-00217-00218-00219-00220-00221-00222-00223-00224-00225-00226-00227-00228-00229-00230-00231-00232-00233-00234-00235-00236-00237-00238-00239-00240-00241-00242-00243-00244-00245-00246-00247-00248-00249-00250-00251-00252-00253-00254-00255-00256-00257-00258-00259-00260-00261-00262-00263-00264-00265-00266-00267-00268-00269-00270-00271-00272-00273-00274-00275-00276-00277-00278-00279-00280-00281-00282-00283-00284-00285-00286-00287-00288-00289-00290-00291-00292-00293" target="_blank"&gt;http://its-t.conocophillips.net/sap/bc/bsp/sap/z_ext_resp/default.htm?WI=000101281590&amp;amp;OBT=ZEPAYINVST&amp;amp;OBK=2008042510064100108846WRMATHE&amp;amp;RSP=2&amp;amp;MSC=00001-00002-00003-00004-00005-00006-00007-00008-00009-00010-00011-00012-00013-00014-00015-00016-00017-00018-00019-00020-00021-00022-00023-00024-00025-00026-00027-00028-00029-00030-00031-00032-00033-00034-00035-00036-00037-00038-00039-00040-00041-00042-00043-00044-00045-00046-00047-00048-00049-00050-00051-00052-00053-00054-00055-00056-00057-00058-00059-00060-00061-00062-00063-00064-00065-00066-00067-00068-00069-00070-00071-00072-00073-00074-00075-00076-00077-00078-00079-00080-00081-00082-00083-00084-00085-00086-00087-00088-00089-00090-00091-00092-00093-00094-00095-00096-00097-00098-00099-00100-00101-00102-00103-00104-00105-00106-00107-00108-00109-00110-00111-00112-00113-00114-00115-00116-00117-00118-00119-00120-00121-00122-00123-00124-00125-00126-00127-00128-00129-00130-00131-00132-00133-00134-00135-00136-00137-00138-00139-00140-00141-00142-00143-00144-00145-00146-00147-00148-00149-00150-00151-00152-00153-00154-00155-00156-00157-00158-00159-00160-00161-00162-00163-00164-00165-00166-00167-00168-00169-00170-00171-00172-00173-00174-00175-00176-00177-00178-00179-00180-00181-00182-00183-00184-00185-00186-00187-00188-00189-00190-00191-00192-00193-00194-00195-00196-00197-00198-00199-00200-00201-00202-00203-00204-00205-00206-00207-00208-00209-00210-00211-00212-00213-00214-00215-00216-00217-00218-00219-00220-00221-00222-00223-00224-00225-00226-00227-00228-00229-00230-00231-00232-00233-00234-00235-00236-00237-00238-00239-00240-00241-00242-00243-00244-00245-00246-00247-00248-00249-00250-00251-00252-00253-00254-00255-00256-00257-00258-00259-00260-00261-00262-00263-00264-00265-00266-00267-00268-00269-00270-00271-00272-00273-00274-00275-00276-00277-00278-00279-00280-00281-00282-00283-00284-00285-00286-00287-00288-00289-00290-00291-00292-00293&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 May 2008 12:06:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/csm-redirect-header-length/m-p/966581#M18980</guid>
      <dc:creator>aanelso1</dc:creator>
      <dc:date>2008-05-22T12:06:27Z</dc:date>
    </item>
    <item>
      <title>Re: CSM redirect - header length</title>
      <link>https://community.cisco.com/t5/application-networking/csm-redirect-header-length/m-p/966582#M18981</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I tested your config with 4.2(8) and it works fine.&lt;/P&gt;&lt;P&gt;We had to change the rediret code due to ddts CSCse98829: %p in redirect doesn't work for small GETs which was integrated with 4.2.6&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This change may have solved a problem with long url that had not been detected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can try an upgrade to 4.2.9 to see if that solves your problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 May 2008 14:50:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/csm-redirect-header-length/m-p/966582#M18981</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2008-05-22T14:50:05Z</dc:date>
    </item>
    <item>
      <title>Re: CSM redirect - header length</title>
      <link>https://community.cisco.com/t5/application-networking/csm-redirect-header-length/m-p/966583#M18982</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I upgraded our CSM in our lab environment with 4.2.9. This did not fix the problem. It still appears that the url can be cut down to around 1850 bytes and the CSM will reply with the redirect. But the one that is posted here shows up to be 2277 bytes and it never gets a redirect. I am currently waiting on our TCOM guys (I am a web guy) to get their sniffer set up so I can get a capture file. Hope to post this up this afternoon. Thanks for all of your suggestions and help so far.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 May 2008 16:49:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/csm-redirect-header-length/m-p/966583#M18982</guid>
      <dc:creator>aanelso1</dc:creator>
      <dc:date>2008-05-22T16:49:26Z</dc:date>
    </item>
  </channel>
</rss>

