Ask Your Question

San Diego Photo Urls

asked 2019-03-25 16:47:49 -0600

Should the photo URL protocol behavior described here still apply to the San Diego database?

All of the image URLs I'm getting from GetObject requests are http, not https nor protocol-relative. They all use as the hostname.

Also, based on a random sampling of them, they respond equally on https with a valid certificate, so would it be safe adjust those URLs to https on the way into my database?

RETS Account Details:

Example RETS Request/Response: (Auth/Identity headers removed)

POST /rets/fnisrets.aspx/SPN/getobject HTTP/1.1
Accept: */*
RETS-Version: RETS/1.7.2
Content-Length: 54
Content-Type: application/x-www-form-urlencoded


HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 52
Content-Type: text/xml
Expires: Mon, 01 Jan 0001 00:00:00 GMT
RETS-Server: RETS-Paragon/1.0
RETS-Version: RETS/1.7.2
MIME-Version: 1.0
Content-ID: 190015914
Object-ID: 1
Content-Transfer-Encoding: 8bit
Date: Mon, 25 Mar 2019 21:38:42 GMT

<RETS ReplyCode="0" ReplyText="SUCCESS" >
edit retag flag offensive close merge delete


The note should still be valid. Looking into the issue.

bwolven gravatar imagebwolven ( 2019-03-25 17:53:23 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2019-03-26 09:55:52 -0600

updated 2019-03-26 09:57:45 -0600

Thank you for reporting this.
URLs using "cdnparap*" should work as either "http:" or "https:".
These URLs should have been returned as protocol relative, as documented in the question you referred to.
It has been fixed but was previously configured incorrectly.
Here is what is returned by your example:

edit flag offensive delete link more


Great! Thanks for the quick response and fix!

tmanhollan gravatar imagetmanhollan ( 2019-03-26 09:58:46 -0600 )edit
Login/Signup to Answer

Question Tools

1 follower


Asked: 2019-03-25 16:47:49 -0600

Seen: 438 times

Last updated: Mar 26 '19