12 Replies Latest reply on Sep 3, 2007 1:24 PM by Chris Lowe

    Long URL for gradient resource problematic under IIS 6.0

    Chris Lowe Apprentice

      Hello,

      I have a RichFaces application deployed behind IIS 6.0. IIS 6.0 has a URL length restriction of 260 chars which is causing the request for a gradient image resource to fail with HTTP status of 400 (bad URL). The URL for the resource is massive!

      http://localhost:8080/dcs/public/a4j.res/org.richfaces.renderkit.html.GradientA/DATA/eAFb85aBtbiIQS-.KF2vKDM5Iy0xObVYryg1LyW1KDuzRC-jJDdHzymxONW9KDElMzWvRMUlsSRRgvvk-.vXvjExMTD5MIhmpCYCVTslJmenF-WX5qU45-fkF5UwCPtkJZYl6uck5qXre-aVpKanFln7MAhDVMOMA6stZKhjYKwoALpDEKRFD6RFD6pF6NGCJd8b2y2YGBg9GVjLEnNKUyuKGAQQ6vxKc5NSi9rWTJXlnvKgm4mBoaLgPxAUgwxl.j91z04A-ZVVRA__


      My application functions okay, but looks somewhat bland without the gradients :(

      Does anyone know how I can get around this? On IIS, I tried upping the Http.sys UrlSegmentMaxLength value, but it didn't resolve the issue.

      Is it really necessary for such a long URL for the gradient resource? It's not a Base64 encoding of the actual image is it?

      Regards,

      Chris.