- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Tue, 30 Sep 2014 20:18:02 -0400
- To: Kingsley Idehen <kidehen@openlinksw.com>, public-webpayments@w3.org
On 09/30/2014 05:13 PM, Kingsley Idehen wrote: > I think there's a setting on the server that might targeting our > URIBurner user agent. I am still getting 404's via the agent, but no > so when I use curl directly. I checked, there doesn't seem to be anything targeting the URIBurner UA. You can check that by issuing the following command: curl -vvv -H "Accept: application/xhtml+xml,text/html" -H "User-Agent: http://linkeddata.uriburner.com:8000/vapour#this" https://web-payments.org/vocabs/commerce Here's the result: > GET /vocabs/commerce HTTP/1.1 Host: web-payments.org Accept: > application/xhtml+xml,text/html User-Agent: > http://linkeddata.uriburner.com:8000/vapour#this > < HTTP/1.1 200 OK < ... I also checked the .htaccess file, which doesn't do anything special based on UA: https://github.com/perma-id/w3id.org/blob/master/commerce/.htaccess The Apache config doesn't have anything special about UAs either: <Directory /var/www/w3id.org> Options Indexes FollowSymLinks MultiViews AllowOverride All Require all granted </Directory> If you gave us a full list of headers that your service is sending, we might be able to track down why you're getting a 400 from the service. -- manu -- Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny) Founder/CEO - Digital Bazaar, Inc. blog: The Marathonic Dawn of Web Payments http://manu.sporny.org/2014/dawn-of-web-payments/
Received on Wednesday, 1 October 2014 00:18:32 UTC