Skip to content

Carlos A. Rueda-Velásquez edited this page Dec 12, 2017 · 5 revisions

The Apache settings to dispatch requests against are described below.

Status 2017-12-12

COR-enabled dispatch of requests against

The Apache settings for purposes of resolving requests against via COR are captured in /etc/httpd/conf.d/sweetontology.conf on the same GMU/ECITE server where the COR is deployed:

<VirtualHost *:80>
    DocumentRoot "/var/www/html/"
    AliasMatch "/?" "/var/www/html/"

    RewriteEngine  On
    RewriteRule    ^/ont ^/ont/.* [L,R=404]
    RewriteRule    /(.+)$1 [P,QSA,NE,L]


  • As a placeholder, I created /var/www/html/ and set a corresponding alias for resolution of the domain name itself,

    Such base name request could be used to provide general information about SWEET, etc. Or a simple redirect can also be indicated.

  • Because of the subsequent rule, to avoid confusion in case of requests to or* (/ont is where COR is deployed on, I set a rule to simply respond with 404. Without this rule, this /ont/* request would be processed by the subsequent rule, resulting in some unintended partial dispatch by the COR, which should simply be avoided.

  • Then comes the key rule for the transparent resolution of<NAME> via<NAME>. The flags here mean:

You can’t perform that action at this time.