Ask Your Question

Revision history [back]

NOTE: 5.65 Release - RETS Image URL Breaking Change

As part of our move towards enhancing security across Paragon, we have made changes to the url displayed when accessing RETS Photos. No longer will it display http:// or https:// when accessing photos. This could have an impact on RETS Vendors whose scripts rely upon http:// or https:// to be automatically included will need to be upgraded. However, we are not forcing the use of https://. Vendors can choose to use either http:// or https:// depending on their client’s needs.

NOTE: 5.65 Release - RETS Image URL Breaking Change

As part of our move towards enhancing security across Paragon, we have made changes to the url displayed when accessing RETS Photos. No longer will it display http:// or https:// when accessing photos. This could have an impact on RETS Vendors whose scripts rely upon http:// or https:// to be automatically included will need to be upgraded. However, we are not forcing the use of https://. Vendors can choose to use either http:// or https:// depending on their client’s needs.

NOTE: 5.65 Release - RETS Image URL Possible Breaking Change

As part of our move towards enhancing security across Paragon, with the 5.65 release we have made some changes to Listing Image URLs.

This would apply to Listing Image URLs returned by RETS from GETOBJECT (when Location=1) and also URLs returned by Media resource searches.

For listing images that can be pulled using either HTTP or HTTPS protocol, the url displayed when accessing RETS Photos. No longer URLs will it display http:// be returned in a "Protocol-Relative URL (PRURL)" format.

For example:

  • This: "http://cdnparap50.paragonrels.com/ParagonImages/Property/.../image.JPG"
  • Would become this: "//cdnparap50.paragonrels.com/ParagonImages/Property/.../image.JPG"

For listing images not hosted by Paragon, the URLs may still be returned in protocol specific format containing either "http:" or https:// when accessing photos. This could have an impact on RETS Vendors whose scripts rely upon http:// or https:// to be automatically included will need to be upgraded. However, we are not forcing the use of https://. Vendors can choose to use either http:// or https:// depending on their client’s needs."https:" prefix.

NOTE: 5.65 Release - RETS Image URL Possible Breaking Change

As part of our move towards enhancing security across Paragon, with the 5.65 release on 6/19/2018, we have made some changes to Listing Image URLs.

This would apply to Listing Image URLs returned by RETS from GETOBJECT (when Location=1) and also URLs returned by Media resource searches.

For listing images that can be pulled using either HTTP or HTTPS protocol, the URLs will be returned in a "Protocol-Relative URL (PRURL)" format.

For example:

  • This: "http://cdnparap50.paragonrels.com/ParagonImages/Property/.../image.JPG"
  • Would become this: "//cdnparap50.paragonrels.com/ParagonImages/Property/.../image.JPG"

For listing images not hosted by Paragon, the URLs may still be returned in protocol specific format containing either "http:" or "https:" prefix.

NOTE: 5.65 Release - RETS Image URL Possible Breaking Change

As part of our move towards enhancing security across Paragon, with the 5.65 release on 6/19/2018, we have made some changes to Listing Image URLs.

This would apply to Listing Image URLs returned by RETS from GETOBJECT (when Location=1) and also URLs returned by Media resource searches.

For listing images that can be pulled using either HTTP or HTTPS protocol, the URLs will be returned in a "Protocol-Relative URL (PRURL)" format.

For example:

  • This: "http://cdnparap50.paragonrels.com/ParagonImages/Property/.../image.JPG"
  • Would become this: "//cdnparap50.paragonrels.com/ParagonImages/Property/.../image.JPG"

For listing images not hosted by Paragon, the URLs may still be returned in protocol specific format containing either "http:" or "https:" prefix.

2018-06-21 Update: Agent/ActiveAgent Photo and OfficeLogo URLs are protocol relative too just like the listing URLs.

NOTE: 5.65 Release - RETS Image URL Possible Breaking Change

As part of our move towards enhancing security across Paragon, with the 5.65 release on 6/19/2018, we have made some changes to Listing Image URLs.

This would apply to Listing Image URLs returned by RETS from GETOBJECT (when Location=1) and also URLs returned by Media resource searches.

For listing images that can be pulled using either HTTP or HTTPS protocol, the URLs will be returned in a "Protocol-Relative URL (PRURL)" format.

For example:

  • This: "http://cdnparap50.paragonrels.com/ParagonImages/Property/.../image.JPG"
  • Would become this: "//cdnparap50.paragonrels.com/ParagonImages/Property/.../image.JPG"

For listing images not hosted by Paragon, the URLs may still be returned in protocol specific format containing either "http:" or "https:" prefix.

2018-06-21 Update: Agent/ActiveAgent Photo and OfficeLogo URLs are protocol relative too just like the listing URLs.

Update 2018-07-02: SANDICOR HTTPS Images are not currently available. They should be available sometime in late July.

NOTE: 5.65 Release - RETS Image URL Possible Breaking Change

As part of our move towards enhancing security across Paragon, with the 5.65 release on 6/19/2018, we have made some changes to Listing Image URLs.

This would apply to Listing Image URLs returned by RETS from GETOBJECT (when Location=1) and also URLs returned by Media resource searches.

For listing images that can be pulled using either HTTP or HTTPS protocol, the URLs will be returned in a "Protocol-Relative URL (PRURL)" format.

For example:

  • This: "http://cdnparap50.paragonrels.com/ParagonImages/Property/.../image.JPG"
  • Would become this: "//cdnparap50.paragonrels.com/ParagonImages/Property/.../image.JPG"

For listing images not hosted by Paragon, the URLs may still be returned in protocol specific format containing either "http:" or "https:" prefix.

2018-06-21 Update: Agent/ActiveAgent Photo and OfficeLogo URLs are protocol relative too just like the listing URLs.

Update 2018-07-02: 2018-07-24: SANDICOR HTTPS Images are not currently available. They should be now available sometime in late July.for the image URLs from paragonrels.com.

NOTE: 5.65 Release - RETS Image URL Possible Breaking Change

As part of our move towards enhancing security across Paragon, with the 5.65 release on 6/19/2018, we have made some changes to Listing Image URLs.

This would apply to Listing Image URLs returned by RETS from GETOBJECT (when Location=1) and also URLs returned by Media resource searches.

For listing images that can be pulled using either HTTP or HTTPS protocol, the URLs will be returned in a "Protocol-Relative URL (PRURL)" format.

For example:

  • This: "http://cdnparap50.paragonrels.com/ParagonImages/Property/.../image.JPG"
  • Would become this: "//cdnparap50.paragonrels.com/ParagonImages/Property/.../image.JPG"

For listing images not hosted by Paragon, the URLs may still be returned in protocol specific format containing either "http:" or "https:" prefix.

2018-06-21 Update: Agent/ActiveAgent Photo and OfficeLogo URLs are protocol relative too just like the listing URLs.

Update 2018-07-24: SANDICOR HTTPS Images are now available for the image URLs from paragonrels.com.