Difference between revisions of "User:Thickbrick Sleaford/HTTP Texture Notes"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
My notes on what different server implementations do with GetTexture requests. Maybe this info is useful to someone else too. | My notes on what different server implementations do with GetTexture requests. Maybe this info is useful to someone else too. | ||
Some | Some relevant links: | ||
* [http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.35.1 RFC 2616 section 14] | * [http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.35.1 RFC 2616 section 14] | ||
* [[HTTP_Texture#Partial_Range]] | * [[HTTP_Texture#Partial_Range]] | ||
* [http://pastebin.com/Kc9x5BNS] | * [http://pastebin.com/Kc9x5BNS Techwolf's analysis] | ||
* [https://github.com/thickbrick/imprudence/compare/f2cf12d6bebd98434a0549f031beaac1ff2200c4...http_texture_experiment Relevant changesets in Imprudence 1.4] that try to make http fetching more robust and less reliant on assumptions that are not in the RFC | |||
===Second Life Servers === | ===Second Life Servers === | ||
{{jira|SVC-6396}} When asking for ranges that don't overlap the satisfiable byte range: | |||
$ CAP=<GetTexture cap url> | $ CAP=<GetTexture cap url> | ||
$ UUID=<your texture's UUID> | $ UUID=<your texture's UUID> | ||
$ N=<The known filesize of the texture> | $ N=<The known filesize of the texture> | ||
$ curl --range $N-99999999 --header "Accept: image/x-j2c" -D headers.txt "${CAP}/?texture_id=${UUID}" -o image.j2c | $ curl --range $N-99999999 --header "Accept: image/x-j2c" -D headers.txt "${CAP}/?texture_id=${UUID}" -o image.j2c | ||
Returns the whole texture, with status code 216. What it should do is return status code 416. (See [http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.35.1 RFC 2616]). This may mean that the viewer can't do ranged requests with ranges not beginning the the beginning of the file and expect it to work properly? | Returns the whole texture, with status code 216. What it should do is return status code 416. (See [http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.35.1 RFC 2616]). This may mean that the viewer can't do ranged requests with ranges not beginning the the beginning of the file and expect it to work properly? | ||
* {{jira|SVC-6397}} The response headers are missing ''Content-range:'' header, even when doing a ranged request. | |||
* The request must have an ''"Accept: image/x-j2c"'' header for this to work. | * The request must have an ''"Accept: image/x-j2c"'' header for this to work. | ||
* The response headers contains ''Content-Type: text/html; charset=utf-8'', even when delivering image/x-j2c. | * {{jira|SVC-6073}} The response headers contains ''Content-Type: text/html; charset=utf-8'', even when delivering image/x-j2c. | ||
* {{jira|SVC-6069}} Http GET texture not using keep-alive on sim side (nor client side, so nobody notices...) | |||
* {{jira|SVC-6096}} HTTP-based caching of textures, meta issue. | |||
| Line 25: | Line 26: | ||
* Has a bug where the returned data will be one byte short of the requested data. | * Has a bug where the returned data will be one byte short of the requested data. | ||
====Current Git Version==== | ====Current Git Version==== | ||
* The response has a proper | * The response has a proper ''Content-range:'' header. | ||
* Returns 416 with an empty body if the range is not at least partially satisfiable (i.e. ''start >= length of file''.) | * Returns 416 with an empty body if the range is not at least partially satisfiable (i.e. ''start >= length of file''.) | ||
Revision as of 15:50, 11 November 2010
HTTP Texture Fetching on Different Servers
My notes on what different server implementations do with GetTexture requests. Maybe this info is useful to someone else too.
Some relevant links:
- RFC 2616 section 14
- HTTP_Texture#Partial_Range
- Techwolf's analysis
- Relevant changesets in Imprudence 1.4 that try to make http fetching more robust and less reliant on assumptions that are not in the RFC
Second Life Servers
SVC-6396 When asking for ranges that don't overlap the satisfiable byte range:
$ CAP=<GetTexture cap url>
$ UUID=<your texture's UUID>
$ N=<The known filesize of the texture>
$ curl --range $N-99999999 --header "Accept: image/x-j2c" -D headers.txt "${CAP}/?texture_id=${UUID}" -o image.j2c
Returns the whole texture, with status code 216. What it should do is return status code 416. (See RFC 2616). This may mean that the viewer can't do ranged requests with ranges not beginning the the beginning of the file and expect it to work properly?
- SVC-6397 The response headers are missing Content-range: header, even when doing a ranged request.
- The request must have an "Accept: image/x-j2c" header for this to work.
- SVC-6073 The response headers contains Content-Type: text/html; charset=utf-8, even when delivering image/x-j2c.
- SVC-6069 Http GET texture not using keep-alive on sim side (nor client side, so nobody notices...)
- SVC-6096 HTTP-based caching of textures, meta issue.
OpenSim
Up to and Including 0.7.0.2
- Has a bug where the returned data will be one byte short of the requested data.
Current Git Version
- The response has a proper Content-range: header.
- Returns 416 with an empty body if the range is not at least partially satisfiable (i.e. start >= length of file.)