resources do not resolve
4 views
Skip to first unread message
droi
Jan 9, 2012, 12:23:31 PM1/9/12
to GeoNames
looking up i.e. http://sws.geonames.org/6558306
I got a resource http://sws.geonames.org/2951839/ which does not
resolve. But, using 'www' instead of 'sws' it *does* resolve:
http://www.geonames.org/2951839
I would be glad if you can fix this issue , beeing in a Linked Data
scenario.
-o
I got a resource http://sws.geonames.org/2951839/ which does not
resolve. But, using 'www' instead of 'sws' it *does* resolve:
http://www.geonames.org/2951839
I would be glad if you can fix this issue , beeing in a Linked Data
scenario.
-o
Marc Wick
Jan 10, 2012, 1:27:03 AM1/10/12
to geon...@googlegroups.com
What do you mean by 'it does not resolve'?
Marc
droi
Jan 10, 2012, 4:50:23 AM1/10/12
to GeoNames
ah - nevermind.
It was the missing trailing slash in the case of using links with the
subdomain sws.
Obviously the server automatically appends this missing slash in case
of using the "subdomain" www.
Thus:
http://sws.geonames.org/6558306 #not working
http://www.geonames.org/6558306 #working
http://sws.geonames.org/6558306/ #working
My fault,
oo
It was the missing trailing slash in the case of using links with the
subdomain sws.
Obviously the server automatically appends this missing slash in case
of using the "subdomain" www.
Thus:
http://sws.geonames.org/6558306 #not working
http://www.geonames.org/6558306 #working
http://sws.geonames.org/6558306/ #working
My fault,
oo
Reply all
Reply to author
Forward
0 new messages