URLs. None of the following shall be used as the URL or domain name for the Website or any Microsite: (i) the title or any other element of a Program, including, without limitation, character names and episode names and storylines; and (ii) copyrighted works, trade marks, service marks and other proprietary marks of SPE or a Program; provided that Licensee may use the name of the Program as a subset of Licensee’s name, registered domain name or name of the Licensed Service (e.g., if Licensee’s registered domain name is “Xxxxxxxx.xxx,” and the Program is “XYZ,” Licensee may use the following URL: “Xxxxxxxx.xxx/XXX”); or as a subdirectory to name a page devoted solely to such Program within the Website or a Microsite.
URLs. Partner hereby confirms that it has the ability to access, has accessed, has read and agrees to, the information made available by Cisco at all of the world wide web sites/URLs/addresses/pages referred to anywhere throughout this Agreement. Partner acknowledges that Cisco may modify any URL address or terminate the availability of any information at any address without notice to Reseller.
URLs. It is your responsibility to regularly monitor all applicable URLs referenced in this agreement. You confirm that you have access to the Internet and confirm that prior to entering into this agreement you have read the policies on the websites referenced above and agree to the terms and conditions set out in those policies. You undertake that you will visit the websites referenced above on a regular basis so that you are aware of any amendments Oracle may make to those policies from time to time.
URLs. Company will assign one or more Universal Resource Locators (URL) for the Private Label Site, which GT will promptly implement.
URLs. (i) Company is the owner of all right, title, and interest in and to each URL, free and clear of all liens, security interests, encumbrances, equities and other adverse claims.
(ii) All URLs that have been registered with the appropriate applicable private or public URL registries, domestic and foreign, are currently in compliance with all formal Legal Requirements (including the timely post-registration filing of affidavits of use and incontestability and renewal applications, if any), are valid and enforceable, and are not subject to any maintenance fees or Taxes or actions falling due within ninety (90) days after the Closing Date.
(iii) No registered URL or pending URL application has been or is now involved in any opposition, invalidation, or cancellation and, to the knowledge of Company, no such action is threatened with respect to any of the URLs.
(iv) To the knowledge of Company, there is no potentially interfering URL or URL application of any third party.
(v) To the knowledge of Company, no URL is infringed or has been challenged or threatened in any way. To the knowledge of Company, none of the URLs infringes or is alleged to infringe any URL of any third party.
URLs. (i) Uni-Pixel is the owner of all right, title, and interest in and to each URL, free and clear of all liens, security interests, encumbrances, equities and other adverse claims.
(ii) All URLs that have been registered with the appropriate applicable private or public URL registries, domestic and foreign, are currently in compliance with all formal Legal Requirements (including the timely post-registration filing of affidavits of use and incontestability and renewal applications, if any), are valid and enforceable, and are not subject to any maintenance fees or Taxes or actions falling due within ninety (90) days after the Closing Date.
(iii) No registered URL or pending URL application has been or is now involved in any opposition, invalidation, or cancellation and, to the knowledge of Uni-Pixel, no such action is threatened with respect to any of the URLs.
(iv) To the knowledge of Uni-Pixel, there is no potentially interfering URL or URL application of any third party.
(v) To the knowledge of Uni-Pixel, no URL is infringed or has been challenged or threatened in any way. To the knowledge of Uni-Pixel, none of the URLs infringes or is alleged to infringe any URL of any third party.
URLs. At termination, Digital River will ensure that any links to the Symantec Storefront or related sites hosted by Digital River are appropriately redirected to new mutually agreed upon URLs or IP addresses. Digital River will assist Symantec in redirecting all links, including the forwarding of any Storefront e-mail services, to Symantec or a new Storefront location to be decided at termination.
URLs. During development the following URL for our sandbox environment should be used in place of the production URL. Sandbox: xxxxx://xxx-xxxxxxx.xxxxxxxxxx.xxx/ Production: xxxxx://xxx.xxxxxxxxxx.xxx/ Begin by directing your users to xxxxx://xxx.xxxxxxxxxx.xxx/oauth2/authorize through a GET request with the following URL encoded parameters: response_type Required. A value of code should be used to request an authentication code used later. client_id Required. The client ID you received from Flightdocs when you initially setup. redirect_uri Required. The URL in your app where users will be sent after authorization. state Optional parameter that is round tripped from the server back to your application. This is could be used to redirect the user to the correct resource on your site or to prevent cross-site-request- forgery by validating the state received from Flightdocs. An example request might look like this: GET xxxxx://xxx.xxxxxxxxxx.xxx/oauth2/authorize?response_type=code&client_id=YOUR _CLIENT_ID&redirect_uri=REDIRECT_URI &state=YOUR_STATE_INFORMATION The user will be presented a login page to authenticate with Flightdocs. Flightdocs will handle for validating the user’s credentials and presenting relevant error messages. On successful log in the user will be taken to a consent page to authorize your application to access their Flightdocs account. Clicking “Grant access to Flightdocs” will redirect the user to the URI that you specified with a code parameter and a state parameter if you included one. For example, Flightdocs might redirect to: xxxxx://xxx.xxxx.xxx/flightdocstoken?code=RETURNED_AUTH_CODE &state=YOUR_STATE_INFORMATION The code you receive as a query string parameter is used to get an access token. It is a single use code and is good for no more than 10 minutes. To get an access token you’ll need to make a POST request to xxxxx://xxx.xxxxxxxxxx.xxx/oauth2/token with the following parameters: grant_type Required. A value of authorization_code must be used. code Required. The authorization code you receive previously. client_id Optional. The client ID you received from Flightdocs when you initially setup. client_secret Optional. The client secret you received from Flightdocs when you initially setup. redirect_uri Required. The redirect URI you initially setup with Flightdocs and the same value that was passed in the initial user redirect. The client_id and client_secret can be supplied in the body of the request or in the authorization header. ...
URLs. During development the following URL for our staging environment should be used in place of the production URL. Staging: xxxxx://xxx-xxx.xxxxxxxxxx.xxx/ Production: xxxxx://xxx.xxxxxxxxxx.xxx/ Begin by directing your users to xxxxx://xxx.xxxxxxxxxx.xxx/oauth2/authorize through a GET request with the following URL encoded parameters: response_type Required. A value of code should be used to request an authentication code used later. client_id Required. The client ID you received from Flightdocs when you initially setup.
URLs. Microsoft shall, at its sole cost and expense, obtain and maintain all rights to the URL(s), or any successor URL(s), at which the Private Label Auction Sites are to be located.
