URL with path

What does the extra path (/136550/filename?) information below do? I got same result by removing it.

http://localhost/les971/livelink.exe/136550/file_original?func=doc.Fetch&nodeid=136550

Also the following URL format can be used to fetch an object by name, does it support other object action other than "fetch"? Is this a special format supported by content server or a web server implementation?

http://localhost/les971/livelink.exe/fetch/124491/filename

Find more posts tagged with

Comments

sıɹɥɔ

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

Hi Kevin,

Interesting questions.

The extra path information of an URL (aka "pathinfo") is handled by Content Server when there is no "func" argument in the query string. You can find which values are recognized by using Builder to see the orphans that inherit from WEBDSP's PathInfoHandlers object. For example, on my system I can see "hh", "fetch", "library", "service", and some that can be used with nicknames and/or object IDs: "properties", "open", "overview", "info". The last few are often used to generate "short urls" to items in Content Server e.g.

http://site/cs.exe/info/2000

http://site/cs.exe/open/budget

(If you want to make the URL's even shorter you could use webserver rules.)

As for your question as to why func=doc.fetch includes ID and name in the pathinfo (it's completely independent of the above discussion!), I can guess that the name is there to satisfy certain browsers (especially those that don't follow standards, ahem) in how they interpret a download. Some browsers did (do?) ignore certain response headers in preference to the "filename", i.e. final component in the path, of the request. So, to ensure an appropriate download name and file type is used by the browser Content Server supplies this information there (in addition to what it placed in the headers). For a conformant browser it's redundant, just as you noticed.

Hope this helps,

-chris

From: eLink Entry: Content Server Builder Forum [mailto:componentbuilder@elinkkc.opentext.com]
Sent: Wednesday, February 01, 2012 6:18 AM
To: eLink Recipient
Subject: URL with path

URL with path

Posted by kevin@linkecm.com (Lin, Kevin) On 02-01-2012 09:10

What does the extra path (/136550/filename?) information below do? I got same result by removing it. http://localhost/les971/livelink.exe/136550/file_original?func=doc.Fetch&nodeid=136550 Also the following URL format can be used to fetch an object by name, does it support other object action other than "fetch"? Is this a special format supported by content server or a web server implementation? http://localhost/les971/livelink.exe/fetch/124491/filename

Kevin_Lin

Hey Chris,

Thanks a lot.... exactly what I wanted to know.