org.webpieces.devrouter.impl.notFound.html Maven / Gradle / Ivy

Go to download

Show more of this group Show more artifacts with this name
Show all versions of http-router-dev Show documentation

Library that swaps out specific http-router components to be able to compile code on any request that has changed for use in development servers

There is a newer version: 2.1.1

Show newest version





    You are in the WebPieces Development Server. Your request received a 404.


    Your app's webpage was not found for this reason: ${error}$
    
    
        Existing Routes in your WebApp
        What your webpage looks like in Production
    

    Domain Specific Routes
    Most WebApps will not have Domain Specific Routes.  This is for special situations.  If there is no match on
    any domains, the router skips to the next section looking for a match.  If there is a match on a domain, the router
    narrows to only matching here in this section
        
        #{list items:domains, as:'domain'}#
            ${domain.domain}$
        #{/list}#
        #{else}#
            You have no domain specific routes that match only on domain
        #{/else}#
        
    
    Non Domain Routes
    Webpieces divides url paths up into scopes for speed.  It looks up scope in a Map first and then loops over each route
    in that scopes list doing a Pattern match (so it's good to use scopes to keep code organized and LESS pattern matching).
    Static routes are not shown yet below but we always match on them last since they will be cached.  Not that you would
    have 3000 routes but if you did, you can organize into scopes so that each loop is only 10-30 things instead of looping
    and matching with java's Pattern object 3000 times for the worst case.

            
    ${escOff#routeHtml}$
    
    
    
    TODO: Fill in the module we ended up using and the routes in that module that did not match here to make it
    easy for the developer to see why he got a 404
    

    

    Your app in production will look like what is in this iframe(ie. this is your production 404 page or login page if redirected due to security filter!)