[CONF] Apache Wicket > Request mapping

confluence Tue, 11 Oct 2011 08:06:28 -0700

     Request mapping
    Page edited by             Thomas Götz
    
        

                         Changes (21)
                                 
    

                    
    
            ...

             
To mount a page in Wicket 1.4 the developer had to use _org.apache.wicket.protocol.http.WebApplication_'s: 

            * \#_mount(IRequestTargetUrlCodingStrategy)_ 

            * \#_mount(String, PackageName)_ 

            * \#_mountBookmarkablePage(String, Class<T>)_ 

            * \#_mountBookmarkablePage(String, String, Class<T>)_ 

            an to mount a resource: 

            *  #_mountSharedResource(String, String)_ 

            * \#_mountSharedResource(String, String)_ 

            For more information about these methods check [https://cwiki.apache.org/WICKET/url-coding-strategies.html] 
 
h1. The new way in Wicket 1.5 
 

            *_org.apache.wicket.request.target.coding.IRequestTargetUrlCodingStrategy_* *{_}org.apache.wicket.request.target.coding.IRequestTargetUrlCodingStrategy{_}* interface and all its implementations are replaced with the *_org.apache.wicket.request.IRequestMapper_* *{_}org.apache.wicket.request.IRequestMapper{_}* and its respective implementations. 

             

            To add a mapper into the list of mappers which Wicket will use to process a request use *{_}org.apache.wicket.Application.getRootRequestMapperAsCompound().add(mapperInstance)_*. 

            When a request comes Wicket will ask all registered mappers whether they are able to process the request. Mappers with bigger *{_}org.apache.wicket.request.IRequestMapper.getCompatibilityScore(Request)_* are asked first. So Wicket calls *{_}org.apache.wicket.request.IRequestMapper.mapRequest(Request)_* for each mapper and if it returns non-null *_IRequestHandler_* *{_}IRequestHandler{_}* then this is the handler which will be used to process the current request. In *_\#mapRequest(Request)_* the mapper have to check request's segments (this is similar to *{_}httpServletRequest#getPath()_*) and request's parameters (GET and POST) and decide whether they match to the mapper's functionality. For example *_org.apache.wicket.request.mapper.HomePageMapper_* *{_}org.apache.wicket.request.mapper.HomePageMapper{_}* is the mapper used to process all requests without any segments, i.e. requests to '/' with or without any query parameters. 

            The actual processing of the request is being done with *{_}org.apache.wicket.request.IRequestHandler.respond(IRequestCycle)_*. During the processing Wicket asks the mappers to create a *_org.apache.wicket.request.Url_* *{_}org.apache.wicket.request.Url{_}* objects for each callback handler (e.g. link, form, ....) via *{_}org.apache.wicket.request.IRequestMapper.mapHandler(IRequestHandler)_*. 

             

            Sometimes you may want a specific IRequestMapper to be process all incoming requests. To do this you should use *{_}org.apache.wicket.Application.setRootRequestMapper(IRequestMapper)_*. This mapper may manipulate the Request's Url and then pass it for further processing to the registered non-root mappers. For examples of this idea see the source code of *_org.apache.wicket.request.mapper.CryptoMapper_* *{_}org.apache.wicket.request.mapper.CryptoMapper{_}* and *_org.apache.wicket.protocol.https.HttpsMapper_* *{_}org.apache.wicket.protocol.https.HttpsMapper{_}* 

             
h2. Default mapper implementations 

            ...

             
This mapper decodes and encodes bookmarkable URLs like: 

            * _/wicket/bookmarkable/com.example.pages.MyPage_ - \- using _BookmarkablePageRequestHandler_ for stateless pages and using RenderPageRequestHandler for stateful/hybrid pages 

            * _/wicket/bookmarkable/com.example.pages.MyPage?2-click-foo-bar-baz_ - \- using _BookmarkableListenerInterfaceRequestHandler_ to process bookmarkable listeners (e.g. Behavior). 

             
This mapper is also pre-configured and there is no need to register it. 
 

            To change 'wicket' and 'bookmarkable' segments in the Url to something else see *{_}org.apache.wicket.request.mapper.IMapperContext.getNamespace()_* (the default implementation can be replaced with *{_}org.apache.wicket.Application.newMapperContext()_*). 

             
h3. _MountedMapper_ 

            ...

            This mapper is similar to _BookmarkableMapper_ but the difference is that the user application defines the mount point where this mapper matches. 
For example: 

            * _/path/to/page1_ 

            * _/path/to/page1N_ 

             * _/path/to/pageN_ 

            * _/path/to/page?2-5.click.1-foo-bar-baz_ (2 is the page version, 5 is render count, 1 is behavior index) 

             
Usage: 

            ...

            {code} 
 

            This mapper is a combination of all *_IRequestTargetUrlCodingStrategy_* *{_}IRequestTargetUrlCodingStrategy{_}* implementations from Wicket 1.4. It supports: 

            # Indexed parameters: 

            mountPage("/page", MyPage.class); 
Now a request to "/page/a/b/c" will be handled by MyPage and the parameters can be get with PageParameters.get(int) (e.g. _parameters.get(2)_ will return "c") 

            ...

             
# Optional named parameters: 

            mountPage("/page/$\{named1\}/\#\{named2\}", MyPage.class); 

            This means the second parameter is optional. Requests to "/page/a/b" ,  "/page/a/b/" and "/page/a/" will be handled by MyPage and the parameters can be get with PageParameters.get(String) (e.g. _parameters.get("named2")_ will return "b" for the first case and *_null_* *{_}null{_}* for the second). 

            The mapper is smart enough to handle optional named parameters in any segment, not just the last one. 
 

            ...

            	super.init(); 
 

            IRequestMapper cryptoMapper = new CryptoMapper(getRootRequestMapper(), this)); 

            	setRootRequestMapper(cryptoMapper); 
} 

            ...

              	{ 
  		super.init(); 

             

              		getRootRequestMapperAsCompound().add(new MountedMapper("secured", HttpsPage.class)); 

             

              		setRootRequestMapper(new HttpsMapper(getRootRequestMapper(), new HttpsConfig(80, 443))); 
  	} 

            ...

            /** 
 * {@link UrlRenderer} which generates absolute urls 

             * 

             * @author Bas 

             * 

             */ 
public class AbsoluteUrlRenderer extends UrlRenderer 

            ...

            /** 
 * {@link RequestCycle} provider which overrides the {@link UrlRenderer} to generate absolute links. 

             * 

             * @see {@link AbsoluteUrlRenderer} 
 * @see {@link RequestCycle#getUrlRenderer()} 

             * 

             * @author Bas 

             * 

             */ 
public class AbsoluteUrlRequestCycleProvider implements IRequestCycleProvider 

            ...

            {code} 
 

            In your Application#init() method, call 

             
{code} 

            ...

    
            
    
                            Full Content
                    
        How it was in Wicket 1.4

To mount a page in Wicket 1.4 the developer had to use org.apache.wicket.protocol.http.WebApplication's:

	#mount(IRequestTargetUrlCodingStrategy)
	#mount(String, PackageName)
	#mountBookmarkablePage(String, Class<T>)
	#mountBookmarkablePage(String, String, Class<T>)

an to mount a resource:
	#mountSharedResource(String, String)

For more information about these methods check https://cwiki.apache.org/WICKET/url-coding-strategies.html



The new way in Wicket 1.5

org.apache.wicket.request.target.coding.IRequestTargetUrlCodingStrategy interface and all its implementations are replaced with the org.apache.wicket.request.IRequestMapper and its respective implementations.

To add a mapper into the list of mappers which Wicket will use to process a request use org.apache.wicket.Application.getRootRequestMapperAsCompound().add(mapperInstance).

When a request comes Wicket will ask all registered mappers whether they are able to process the request. Mappers with bigger org.apache.wicket.request.IRequestMapper.getCompatibilityScore(Request) are asked first. So Wicket calls org.apache.wicket.request.IRequestMapper.mapRequest(Request) for each mapper and if it returns non-null IRequestHandler then this is the handler which will be used to process the current request. In #mapRequest(Request) the mapper have to check request's segments (this is similar to httpServletRequest#getPath()) and request's parameters (GET and POST) and decide whether they match to the mapper's functionality. For example org.apache.wicket.request.mapper.HomePageMapper is the mapper used to process all requests without any segments, i.e. requests to '/' with or without any query parameters.

The actual processing of the request is being done with org.apache.wicket.request.IRequestHandler.respond(IRequestCycle). During the processing Wicket asks the mappers to create a org.apache.wicket.request.Url objects for each callback handler (e.g. link, form, ....) via org.apache.wicket.request.IRequestMapper.mapHandler(IRequestHandler).

Sometimes you may want a specific IRequestMapper to be process all incoming requests. To do this you should use org.apache.wicket.Application.setRootRequestMapper(IRequestMapper). This mapper may manipulate the Request's Url and then pass it for further processing to the registered non-root mappers. For examples of this idea see the source code of org.apache.wicket.request.mapper.CryptoMapper and org.apache.wicket.protocol.https.HttpsMapper

Default mapper implementations

HomePageMapper

This mapper is pre-configured by Wicket and there is no need to register it. It is used to create IRequestHandler for requests to the root ('/') of the application context.

BookmarkableMapper

This mapper decodes and encodes bookmarkable URLs like:

	/wicket/bookmarkable/com.example.pages.MyPage - using BookmarkablePageRequestHandler for stateless pages and using RenderPageRequestHandler for stateful/hybrid pages
	/wicket/bookmarkable/com.example.pages.MyPage?2-click-foo-bar-baz - using BookmarkableListenerInterfaceRequestHandler to process bookmarkable listeners (e.g. Behavior).



This mapper is also pre-configured and there is no need to register it.

To change 'wicket' and 'bookmarkable' segments in the Url to something else see org.apache.wicket.request.mapper.IMapperContext.getNamespace() (the default implementation can be replaced with org.apache.wicket.Application.newMapperContext()).

MountedMapper

This mapper is similar to BookmarkableMapper but the difference is that the user application defines the mount point where this mapper matches.

For example:

	/path/to/page1
	/path/to/pageN
	/path/to/page?2-5.click.1-foo-bar-baz (2 is the page version, 5 is render count, 1 is behavior index)



Usage:

MyApp.java:

public void init() {
	super.init();

	getRootRequestMapperAsCompound().add(new MountedMapper("/mount/point", MyPage.class));
	mountPage("/mount/point", MyPage.class); // convenient method doing the same as above
}



This mapper is a combination of all IRequestTargetUrlCodingStrategy implementations from Wicket 1.4. It supports:

	Indexed parameters:

mountPage("/page", MyPage.class);

Now a request to "/page/a/b/c" will be handled by MyPage and the parameters can be get with PageParameters.get(int) (e.g. parameters.get(2) will return "c")




	Named parameters:

mountPage("/page/${named1}/${named2}", MyPage.class);

Now a request to "/page/a/b" will be handled by MyPage and the parameters can be get with PageParameters.get(String) (e.g. parameters.get("named1") will return "a")




	Optional named parameters:

mountPage("/page/${named1}/#{named2}", MyPage.class);

This means the second parameter is optional. Requests to "/page/a/b" ,  "/page/a/b/" and "/page/a/" will be handled by MyPage and the parameters can be get with PageParameters.get(String) (e.g. parameters.get("named2") will return "b" for the first case and null for the second).

The mapper is smart enough to handle optional named parameters in any segment, not just the last one.




	Query parameters:

mountPage("/page", MyPage.class);

Now a request to "/page?a=a1&b=b1" will be handled by MyPage and the parameters can be get with PageParameters.get(String) (e.g. parameters.get("a") will return "a1")



The mapper can handle a mix of the supported parameters - indexed + named + query.

PackageMapper

This mapper can mount a whole package. That is you mount a single page with a mount path prefix and then the mapper knows how to map all Page implementations in that package.

Usage:

MyApp.java:

public void init() {
	super.init();

        getRootRequestMapperAsCompound().add(
			new MountMapper("/mount/point", new PackageMapper(
				PackageName.forClass(Page3.class))));
        mountPackage("/mount/point", Page3.class);
}



Assuming that PageA package is "com.example.pages" a request to "/mount/point/PageB" will use com.example.pages.PageB if it exists and is an instance of Page.

ResourceMapper

A mapper which mounts ResourceReference implementations.

Usage:

MyApp.java:

public void init() {
	super.init();

	getRootRequestMapperAsCompound().add(new ResourceMapper("/company/logo", new PackageResourceReference(MyPage.class, "res/logo.gif")));
	mountResource("/company/logo", new PackageResourceReference(MyPage.class, "res/logo.gif"))); // convenient method doing the same as above
}



CryptoMapper

A wrapper around another mapper which will encrypt/decrypt the URLs generated by the inner one.

Usage:

MyApp.java:

public void init() {
	super.init();

        IRequestMapper cryptoMapper = new CryptoMapper(getRootRequestMapper(), this);
	setRootRequestMapper(cryptoMapper);
}





HttpsMapper

A mapper which makes a redirect to the same URL with HTTPS protocol if the requested page is annotated with @RequireHttps or to HTTP protocol if the last processed page had @RequireHttps and the one going to be processed has no such annotation.

Usage:


 public class MyApplication extends WebApplication
 {
  	public void init()
  	{
  		super.init();

  		getRootRequestMapperAsCompound().add(new MountedMapper("secured", HttpsPage.class));

  		setRootRequestMapper(new HttpsMapper(getRootRequestMapper(), new HttpsConfig(80, 443)));
  	}
 }



Making all urls absolute

You can override RequestCycle#newUrlRenderer() with a different UrlRenderer to force all links to be absolute.


import org.apache.wicket.request.Request;
import org.apache.wicket.request.Url;
import org.apache.wicket.request.UrlRenderer;
import org.apache.wicket.util.lang.Args;
import org.apache.wicket.util.string.Strings;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

/**
 * {@link UrlRenderer} which generates absolute urls
 *
 * @author Bas
 *
 */
public class AbsoluteUrlRenderer extends UrlRenderer
{
    private static final Logger log = LoggerFactory.getLogger( AbsoluteUrlRenderer.class );

    private final Url contextUrl, filterUrl;

    public AbsoluteUrlRenderer( Request request, String prefix )
    {
        super( request );

        this.contextUrl = buildContextUrl( request, prefix );
        this.filterUrl = buildFilterUrl( request, prefix );

        log.debug( "Prefix for absolute urls: {}", filterUrl );
    }

    @Override
    public String renderRelativeUrl( Url url )
    {
        Args.notNull( url, "url" );

        if( url.isAbsolute() )
        {
            return url.toString();
        }
        else
        {
            Url absolute = fromFilterRelativeToAbsolute( url );
            log.debug( "renderRelativeUrl: {} => {}", url, absolute );

            String renderedUrl = absolute.toString();
            return Strings.isEmpty( renderedUrl ) ? "." : renderedUrl;
        }
    }

    @Override
    public String renderContextRelativeUrl( String url )
    {
        Args.notNull( url, "url" );

        // Prevent prefixing a url twice
        if( url.startsWith( contextUrl.toString() ) )
        {
            return url;
        }

        if( url.startsWith( "/" ) )
        {
            url = "" 1 );
        }

        Url relativeUrl = Url.parse( url );
        Url absoluteUrl = fromContextRelativeToAbsolute( relativeUrl );
        log.debug( "renderContextRelativeUrl: {} -> {}", relativeUrl, absoluteUrl );

        return absoluteUrl.toString();
    }

    private Url buildContextUrl( Request request, String prefix )
    {
        Url url = "" class="code-keyword">new Url();

        if( prefix != null && prefix.length() > 0 )
        {
            url.getSegments().addAll( Url.parse( prefix ).getSegments() );
        }

        String contextPath = request.getContextPath();
        if( contextPath.length() > 0 )
        {
            url.getSegments().addAll( Url.parse( contextPath.substring( 1 ) ).getSegments() );
        }

        if( !url.isAbsolute() )
        {
            url.getSegments().add( 0, "" );
        }

        return url;
    }

    private Url buildFilterUrl( Request request, String prefix )
    {
        Url url = "" request, prefix );

        String filterPath = request.getFilterPath();
        if( filterPath.length() > 0 )
        {
            url.getSegments().addAll( Url.parse( filterPath.substring( 1 ) ).getSegments() );
        }

        return url;
    }

    private Url fromContextRelativeToAbsolute( Url url )
    {
        Url absolute = new Url( url );
        absolute.prependLeadingSegments( contextUrl.getSegments() );

        return absolute;
    }

    private Url fromFilterRelativeToAbsolute( Url url )
    {
        Url absolute = new Url( url );
        absolute.prependLeadingSegments( filterUrl.getSegments() );

        return absolute;
    }

}



There is an optional prefix parameter which you can supply to the constructor to set a fixed prefix. The sole purpose of this prefix is to handle the case where the app server is behind a reverse proxy, and the reverse proxy maps a folder to a root-mapped application. E.g. the reverse proxy maps "/app" to an app running at "/" with the WicketFilter handling "/*". All urls need to be prefixed with "/app", but AbsoluteUrlRenderer cannot detect this.

Installing this custom UrlRenderer can be done by installing a custom IRequestCycleProvider:


import org.apache.wicket.IRequestCycleProvider;
import org.apache.wicket.request.UrlRenderer;
import org.apache.wicket.request.cycle.RequestCycle;
import org.apache.wicket.request.cycle.RequestCycleContext;

/**
 * {@link RequestCycle} provider which overrides the {@link UrlRenderer} to generate absolute links.
 *
 * @see {@link AbsoluteUrlRenderer}
 * @see {@link RequestCycle#getUrlRenderer()}
 *
 * @author Bas
 *
 */
public class AbsoluteUrlRequestCycleProvider implements IRequestCycleProvider
{
    private final String prefix;

    public AbsoluteUrlRequestCycleProvider()
    {
        this( null );
    }

    public AbsoluteUrlRequestCycleProvider( String prefix )
    {
        this.prefix = prefix;
    }

    @Override
    public RequestCycle get( RequestCycleContext context )
    {
        return new RequestCycle( context )
        {

            @Override
            protected UrlRenderer newUrlRenderer()
            {

                return new AbsoluteUrlRenderer( getRequest(), prefix );
            }

        };
    }
}



In your Application#init() method, call


setRequestCycleProvider( new AbsoluteUrlRequestCycleProvider() );


    
        
        
            Change Notification Preferences
        
        View Online
        |
        View Changes
                |
        Add Comment
 ...
 To mount a page in Wicket 1.4 the developer had to use _org.apache.wicket.protocol.http.WebApplication_'s:
 * \#_mount(IRequestTargetUrlCodingStrategy)_
 * \#_mount(String, PackageName)_
 * \#_mountBookmarkablePage(String, Class<T>)_
 * \#_mountBookmarkablePage(String, String, Class<T>)_
 an to mount a resource:
-*  #_mountSharedResource(String, String)_
+* \#_mountSharedResource(String, String)_
 For more information about these methods check [https://cwiki.apache.org/WICKET/url-coding-strategies.html] 
 
h1. The new way in Wicket 1.5
 *_org.apache.wicket.request.target.coding.IRequestTargetUrlCodingStrategy_* *{_}org.apache.wicket.request.target.coding.IRequestTargetUrlCodingStrategy{_}* interface and all its implementations are replaced with the *_org.apache.wicket.request.IRequestMapper_* *{_}org.apache.wicket.request.IRequestMapper{_}* and its respective implementations.
 To add a mapper into the list of mappers which Wicket will use to process a request use *{_}org.apache.wicket.Application.getRootRequestMapperAsCompound().add(mapperInstance)_*.
 When a request comes Wicket will ask all registered mappers whether they are able to process the request. Mappers with bigger *{_}org.apache.wicket.request.IRequestMapper.getCompatibilityScore(Request)_* are asked first. So Wicket calls *{_}org.apache.wicket.request.IRequestMapper.mapRequest(Request)_* for each mapper and if it returns non-null *_IRequestHandler_* *{_}IRequestHandler{_}* then this is the handler which will be used to process the current request. In *_\#mapRequest(Request)_* the mapper have to check request's segments (this is similar to *{_}httpServletRequest#getPath()_*) and request's parameters (GET and POST) and decide whether they match to the mapper's functionality. For example *_org.apache.wicket.request.mapper.HomePageMapper_* *{_}org.apache.wicket.request.mapper.HomePageMapper{_}* is the mapper used to process all requests without any segments, i.e. requests to '/' with or without any query parameters.
 The actual processing of the request is being done with *{_}org.apache.wicket.request.IRequestHandler.respond(IRequestCycle)_*. During the processing Wicket asks the mappers to create a *_org.apache.wicket.request.Url_* *{_}org.apache.wicket.request.Url{_}* objects for each callback handler (e.g. link, form, ....) via *{_}org.apache.wicket.request.IRequestMapper.mapHandler(IRequestHandler)_*.
 Sometimes you may want a specific IRequestMapper to be process all incoming requests. To do this you should use *{_}org.apache.wicket.Application.setRootRequestMapper(IRequestMapper)_*. This mapper may manipulate the Request's Url and then pass it for further processing to the registered non-root mappers. For examples of this idea see the source code of *_org.apache.wicket.request.mapper.CryptoMapper_* *{_}org.apache.wicket.request.mapper.CryptoMapper{_}* and *_org.apache.wicket.protocol.https.HttpsMapper_* *{_}org.apache.wicket.protocol.https.HttpsMapper{_}*
 h2. Default mapper implementations
 ...
 This mapper decodes and encodes bookmarkable URLs like:
 * _/wicket/bookmarkable/com.example.pages.MyPage_ - \- using _BookmarkablePageRequestHandler_ for stateless pages and using RenderPageRequestHandler for stateful/hybrid pages
 * _/wicket/bookmarkable/com.example.pages.MyPage?2-click-foo-bar-baz_ - \- using _BookmarkableListenerInterfaceRequestHandler_ to process bookmarkable listeners (e.g. Behavior).
 This mapper is also pre-configured and there is no need to register it.
 To change 'wicket' and 'bookmarkable' segments in the Url to something else see *{_}org.apache.wicket.request.mapper.IMapperContext.getNamespace()_* (the default implementation can be replaced with *{_}org.apache.wicket.Application.newMapperContext()_*).
 h3. _MountedMapper_
 ...
 This mapper is similar to _BookmarkableMapper_ but the difference is that the user application defines the mount point where this mapper matches. 
For example:
+* _/path/to/page1_
 * _/path/to/page1N_
- * _/path/to/pageN_
 * _/path/to/page?2-5.click.1-foo-bar-baz_ (2 is the page version, 5 is render count, 1 is behavior index)
 Usage:
 ...
 {code}
 This mapper is a combination of all *_IRequestTargetUrlCodingStrategy_* *{_}IRequestTargetUrlCodingStrategy{_}* implementations from Wicket 1.4. It supports:
 # Indexed parameters:
 mountPage("/page", MyPage.class); 
Now a request to "/page/a/b/c" will be handled by MyPage and the parameters can be get with PageParameters.get(int) (e.g. _parameters.get(2)_ will return "c")
 ...
 # Optional named parameters:
 mountPage("/page/$\{named1\}/\#\{named2\}", MyPage.class);
 This means the second parameter is optional. Requests to "/page/a/b" ,  "/page/a/b/" and "/page/a/" will be handled by MyPage and the parameters can be get with PageParameters.get(String) (e.g. _parameters.get("named2")_ will return "b" for the first case and *_null_* *{_}null{_}* for the second).
 The mapper is smart enough to handle optional named parameters in any segment, not just the last one.
 ...
 	super.init();
 IRequestMapper cryptoMapper = new CryptoMapper(getRootRequestMapper(), this));
 	setRootRequestMapper(cryptoMapper); 
}
 ...
   	{ 
  		super.init();
   		getRootRequestMapperAsCompound().add(new MountedMapper("secured", HttpsPage.class));
   		setRootRequestMapper(new HttpsMapper(getRootRequestMapper(), new HttpsConfig(80, 443))); 
  	}
 ...
 /** 
 * {@link UrlRenderer} which generates absolute urls
  *
  * @author Bas
  *
  */ 
public class AbsoluteUrlRenderer extends UrlRenderer
 ...
 /** 
 * {@link RequestCycle} provider which overrides the {@link UrlRenderer} to generate absolute links.
  *
  * @see {@link AbsoluteUrlRenderer} 
 * @see {@link RequestCycle#getUrlRenderer()}
  *
  * @author Bas
  *
  */ 
public class AbsoluteUrlRequestCycleProvider implements IRequestCycleProvider
 ...
 {code}
 In your Application#init() method, call
 {code}
 ...

[CONF] Apache Wicket > Request mapping

Request mapping

Page edited by Thomas Götz

Changes (21)

Full Content

How it was in Wicket 1.4

The new way in Wicket 1.5

Default mapper implementations

HomePageMapper

BookmarkableMapper

MountedMapper

PackageMapper

ResourceMapper

CryptoMapper

HttpsMapper

Making all urls absolute

Reply via email to