You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Henri Dupre (JIRA)" <ta...@jakarta.apache.org> on 2005/09/23 22:24:28 UTC

[jira] Created: (TAPESTRY-664) Issue with Asset URLs and proxies

Issue with Asset URLs and proxies
---------------------------------

         Key: TAPESTRY-664
         URL: http://issues.apache.org/jira/browse/TAPESTRY-664
     Project: Tapestry
        Type: Bug
    Versions: 4.0, 3.0.3, 3.0.2, 3.0.1    
    Reporter: Henri Dupre


This is an issue that I have been having with Tapestry 3 but I believe it will be the same with Tapestry 4.
We are constantly getting somne  of these errors:

An exception has occurred.

You may continue by restarting the session.

org.apache.tapestry.ApplicationRuntimeException
Service asset requires exactly 2 service parameters.
Stack Trace:

    * org.apache.tapestry.asset.AssetService.service(AssetService.java:136)
    * org.apache.tapestry.engine.AbstractEngine.service(AbstractEngine.java:889) 
...

The source cause is that the URL used is silly:
characterEncoding	UTF-8
contentLength	0
method	GET
protocol	HTTP/1.0
queryString	service=asset&amp;sp=S%2Forg%2Fapache%2Ftapestry%2Fvalid%2FValidator.js&amp;sp=S3dfc7ba91240b3bbd49fbb3ccccefe31

The &amp; are not escaped. I found out that all these silly queries come from proxies!
The proxies seem to somehow parse the html page and generate queries for everything that starts with http.



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


[jira] Commented: (TAPESTRY-664) Issue with Asset URLs and proxies

Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
    [ http://issues.apache.org/jira/browse/TAPESTRY-664?page=comments#action_12330325 ] 

Howard M. Lewis Ship commented on TAPESTRY-664:
-----------------------------------------------

Seriously, how is this Tapestry's issue?  If your proxies are misconfigured then everything breaks ... not just the asset service.

At least it is better in 4.0 with friendly URLs.

> Issue with Asset URLs and proxies
> ---------------------------------
>
>          Key: TAPESTRY-664
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-664
>      Project: Tapestry
>         Type: Bug
>     Versions: 4.0, 3.0.3, 3.0.2, 3.0.1
>     Reporter: Henri Dupre

>
> This is an issue that I have been having with Tapestry 3 but I believe it will be the same with Tapestry 4.
> We are constantly getting somne  of these errors:
> An exception has occurred.
> You may continue by restarting the session.
> org.apache.tapestry.ApplicationRuntimeException
> Service asset requires exactly 2 service parameters.
> Stack Trace:
>     * org.apache.tapestry.asset.AssetService.service(AssetService.java:136)
>     * org.apache.tapestry.engine.AbstractEngine.service(AbstractEngine.java:889) 
> ...
> The source cause is that the URL used is silly:
> characterEncoding	UTF-8
> contentLength	0
> method	GET
> protocol	HTTP/1.0
> queryString	service=asset&amp;sp=S%2Forg%2Fapache%2Ftapestry%2Fvalid%2FValidator.js&amp;sp=S3dfc7ba91240b3bbd49fbb3ccccefe31
> The &amp; are not escaped. I found out that all these silly queries come from proxies!
> The proxies seem to somehow parse the html page and generate queries for everything that starts with http.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


[jira] Commented: (TAPESTRY-664) Issue with Asset URLs and proxies

Posted by "Henri Dupre (JIRA)" <ta...@jakarta.apache.org>.
    [ http://issues.apache.org/jira/browse/TAPESTRY-664?page=comments#action_12330376 ] 

Henri Dupre commented on TAPESTRY-664:
--------------------------------------

Could there be a way to customize the exception behavior, or have more precise exceptions (containing the source)?
So that at least by overriding the exception management (don't know how this has to be done in TP4) in the engine, it is possible to easily ignore this error. If there could be a field in the ApplicationRuntimeException containing the service (source of the exception) it would make easier to ignore this error.

The real issue in large production applications is that this behavior floods the error logs with useless errors.


> Issue with Asset URLs and proxies
> ---------------------------------
>
>          Key: TAPESTRY-664
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-664
>      Project: Tapestry
>         Type: Bug
>     Versions: 3.0.1, 4.0, 3.0.2, 3.0.3
>     Reporter: Henri Dupre

>
> This is an issue that I have been having with Tapestry 3 but I believe it will be the same with Tapestry 4.
> We are constantly getting somne  of these errors:
> An exception has occurred.
> You may continue by restarting the session.
> org.apache.tapestry.ApplicationRuntimeException
> Service asset requires exactly 2 service parameters.
> Stack Trace:
>     * org.apache.tapestry.asset.AssetService.service(AssetService.java:136)
>     * org.apache.tapestry.engine.AbstractEngine.service(AbstractEngine.java:889) 
> ...
> The source cause is that the URL used is silly:
> characterEncoding	UTF-8
> contentLength	0
> method	GET
> protocol	HTTP/1.0
> queryString	service=asset&amp;sp=S%2Forg%2Fapache%2Ftapestry%2Fvalid%2FValidator.js&amp;sp=S3dfc7ba91240b3bbd49fbb3ccccefe31
> The &amp; are not escaped. I found out that all these silly queries come from proxies!
> The proxies seem to somehow parse the html page and generate queries for everything that starts with http.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


[jira] Updated: (TAPESTRY-664) Issue with Asset URLs and proxies

Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
     [ http://issues.apache.org/jira/browse/TAPESTRY-664?page=all ]

Howard M. Lewis Ship updated TAPESTRY-664:
------------------------------------------

    Component: Framework
         type: Wish  (was: Bug)
     Priority: Minor  (was: Major)

> Issue with Asset URLs and proxies
> ---------------------------------
>
>          Key: TAPESTRY-664
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-664
>      Project: Tapestry
>         Type: Wish
>   Components: Framework
>     Versions: 4.0, 3.0.3, 3.0.2, 3.0.1
>     Reporter: Henri Dupre
>     Priority: Minor

>
> This is an issue that I have been having with Tapestry 3 but I believe it will be the same with Tapestry 4.
> We are constantly getting somne  of these errors:
> An exception has occurred.
> You may continue by restarting the session.
> org.apache.tapestry.ApplicationRuntimeException
> Service asset requires exactly 2 service parameters.
> Stack Trace:
>     * org.apache.tapestry.asset.AssetService.service(AssetService.java:136)
>     * org.apache.tapestry.engine.AbstractEngine.service(AbstractEngine.java:889) 
> ...
> The source cause is that the URL used is silly:
> characterEncoding	UTF-8
> contentLength	0
> method	GET
> protocol	HTTP/1.0
> queryString	service=asset&amp;sp=S%2Forg%2Fapache%2Ftapestry%2Fvalid%2FValidator.js&amp;sp=S3dfc7ba91240b3bbd49fbb3ccccefe31
> The &amp; are not escaped. I found out that all these silly queries come from proxies!
> The proxies seem to somehow parse the html page and generate queries for everything that starts with http.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


[jira] Resolved: (TAPESTRY-664) Issue with Asset URLs and proxies

Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
     [ http://issues.apache.org/jira/browse/TAPESTRY-664?page=all ]

Jesse Kuhnert resolved TAPESTRY-664.
------------------------------------

    Fix Version/s: 4.0.2
       Resolution: Fixed

Howard added a whole new set of exception presenting hivemind configuration points. The presentation of these errors can be overriden.

> Issue with Asset URLs and proxies
> ---------------------------------
>
>                 Key: TAPESTRY-664
>                 URL: http://issues.apache.org/jira/browse/TAPESTRY-664
>             Project: Tapestry
>          Issue Type: Wish
>          Components: Framework
>    Affects Versions: 3.0.1, 4.0, 3.0.2, 3.0.3
>            Reporter: Henri Dupre
>            Priority: Minor
>             Fix For: 4.0.2
>
>
> This is an issue that I have been having with Tapestry 3 but I believe it will be the same with Tapestry 4.
> We are constantly getting somne  of these errors:
> An exception has occurred.
> You may continue by restarting the session.
> org.apache.tapestry.ApplicationRuntimeException
> Service asset requires exactly 2 service parameters.
> Stack Trace:
>     * org.apache.tapestry.asset.AssetService.service(AssetService.java:136)
>     * org.apache.tapestry.engine.AbstractEngine.service(AbstractEngine.java:889) 
> ...
> The source cause is that the URL used is silly:
> characterEncoding	UTF-8
> contentLength	0
> method	GET
> protocol	HTTP/1.0
> queryString	service=asset&amp;sp=S%2Forg%2Fapache%2Ftapestry%2Fvalid%2FValidator.js&amp;sp=S3dfc7ba91240b3bbd49fbb3ccccefe31
> The &amp; are not escaped. I found out that all these silly queries come from proxies!
> The proxies seem to somehow parse the html page and generate queries for everything that starts with http.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org