edited body

Source Link

edited Mar 14, 2017 at 8:52

137.7k
13
289
751

[CASE:3855442] was created

It seems that sources of URL* related features are not initialized properly which leads to problems in many cases.

Please follow those steps to reproduce the problem:

Let's deploy a test api:

  api = First @ CloudDeploy @ Delayed @ HTTPErrorResponse[404]

Check:
```
  URLRead[api]
```

So far so good

Copy api url string and try

    URLRead["https://www.wolframcloud.com/objects/...."]

Should return 404, nothing unexpected.

Now Quit[] the Kernel and run the manual check again:

    URLRead["https://www.wolframcloud.com/objects/...."]

What?

What is more interesting, deploy another api and run manual test for the old url, now it works again...

How to classify this feature? What to call to have stuff initialized/loaded properly?

[CASE:3855442] was created

It seems that sources of URL* related features are not initialized properly which leads to problems in many cases.

Please follow those steps to reproduce the problem:

Let's deploy a test api:

  api = First @ CloudDeploy @ Delayed @ HTTPErrorResponse[404]

Check:
```
  URLRead[api]
```

So far so good

Copy api url string and try

    URLRead["https://www.wolframcloud.com/objects/...."]

Should return 404, nothing unexpected.

Now Quit[] the Kernel and run the manual check again:

    URLRead["https://www.wolframcloud.com/objects/...."]

What?

What is more interesting, deploy another api and run manual test for the old url, now it works again...

How to classify this feature? What to call to have stuff initialized/loaded properly?

It seems that sources of URL* related features are not initialized properly which leads to problems in many cases.

Please follow those steps to reproduce the problem:

Let's deploy a test api:

  api = First @ CloudDeploy @ Delayed @ HTTPErrorResponse[404]

Check:
```
  URLRead[api]
```

So far so good

Copy api url string and try

    URLRead["https://www.wolframcloud.com/objects/...."]

Should return 404, nothing unexpected.

Now Quit[] the Kernel and run the manual check again:

    URLRead["https://www.wolframcloud.com/objects/...."]

What?

What is more interesting, deploy another api and run manual test for the old url, now it works again...

How to classify this feature? What to call to have stuff initialized/loaded properly?

[CASE:3855442] was created

Tweeted twitter.com/StackMma/status/839524855871586304

occurred Mar 8, 2017 at 17:14

edited title

Source Link

edited Mar 8, 2017 at 13:02

Kuba

137.7k
13
289
751

Inconsistent behavior of HTTPResponse handling

[CASE:3855442] was created

It seems that sources of URL* related features are not initialized properly which leads to problems in many cases.

Please follow those steps to reproduce the problem:

Let's deploy a test api:

  api = First @ CloudDeploy @ Delayed @ HTTPErrorResponse[404]

Check:
```
  URLRead[api]
```

So far so good

Copy api url string and try

    URLRead["https://www.wolframcloud.com/objects/...."]

Should return 404, nothing unexpected.

Now Quit[] the Kernel and run the manual check again:

    URLRead["https://www.wolframcloud.com/objects/...."]

What? I agree that returning 404 this way may not be the best idea but I expect at least consistent results.

What is more interesting, deploy another api and run manual test for the old url, now it works again...

How to classify this feature? What to call to have stuff initialized/loaded properly?

Inconsistent behavior of HTTPResponse handling

[CASE:3855442] was created

It seems that sources of URL* related features are not initialized properly which leads to problems in many cases.

Please follow those steps to reproduce the problem:

Let's deploy a test api:

  api = First @ CloudDeploy @ Delayed @ HTTPErrorResponse[404]

Check:
```
  URLRead[api]
```

So far so good

Copy api url string and try

    URLRead["https://www.wolframcloud.com/objects/...."]

Should return 404, nothing unexpected.

Now Quit[] the Kernel and run the manual check again:

    URLRead["https://www.wolframcloud.com/objects/...."]

What? I agree that returning 404 this way may not be the best idea but I expect at least consistent results.

What is more interesting, deploy another api and run manual test for the old url, now it works again...

How to classify this feature? What to call to have stuff initialized/loaded properly?

Inconsistent HTTPResponse handling

[CASE:3855442] was created

It seems that sources of URL* related features are not initialized properly which leads to problems in many cases.

Please follow those steps to reproduce the problem:

Let's deploy a test api:

  api = First @ CloudDeploy @ Delayed @ HTTPErrorResponse[404]

Check:
```
  URLRead[api]
```

So far so good

Copy api url string and try

    URLRead["https://www.wolframcloud.com/objects/...."]

Should return 404, nothing unexpected.

Now Quit[] the Kernel and run the manual check again:

    URLRead["https://www.wolframcloud.com/objects/...."]

What?

What is more interesting, deploy another api and run manual test for the old url, now it works again...

How to classify this feature? What to call to have stuff initialized/loaded properly?

deleted 87 characters in body; edited title

Source Link

edited Mar 8, 2017 at 12:55

Kuba

137.7k
13
289
751

Inconsistent behavior of URLReadHTTPResponse handling

[CASE:3855442] was created

It seems that sources of URL* related features are not initialized properly which leads to problems in many cases.

Please follow those steps to reproduce the problem:

Let's deploy a test api:

  api = First @ CloudDeploy @ APIFunction[
      {}
    , HTTPResponse["", <|"Content" -> "TEST", "StatusCode" -> 404|>] &
Delayed @ ]HTTPErrorResponse[404]

Check:
```
  URLRead[api]
```

So far so good

Copy api url string and try

    URLRead["https://www.wolframcloud.com/objects/...."]

Should return 404, nothing unexpected.

Now Quit[] the Kernel and run the manual check again:

    URLRead["https://www.wolframcloud.com/objects/...."]

What? I agree that returning 404 this way may not be the best idea but I expect at least consistent results.

What is more interesting, deploy another api and run manual test for the old url, now it works again...

How to classify this feature? What to call to have stuff initialized/loaded properly?

Inconsistent behavior of URLRead

[CASE:3855442] was created

It seems that sources of URL* related features are not initialized properly which leads to problems in many cases.

Please follow those steps to reproduce the problem:

Let's deploy a test api:

  api = First @ CloudDeploy @ APIFunction[
      {}
    , HTTPResponse["", <|"Content" -> "TEST", "StatusCode" -> 404|>] &
  ]

Check:
```
  URLRead[api]
```

So far so good

Copy api url string and try

    URLRead["https://www.wolframcloud.com/objects/...."]

Should return 404, nothing unexpected.

Now Quit[] the Kernel and run the manual check again:

    URLRead["https://www.wolframcloud.com/objects/...."]

What? I agree that returning 404 this way may not be the best idea but I expect at least consistent results.

What is more interesting, deploy another api and run manual test for the old url, now it works again...

How to classify this feature? What to call to have stuff initialized/loaded properly?

Inconsistent behavior of HTTPResponse handling

[CASE:3855442] was created

It seems that sources of URL* related features are not initialized properly which leads to problems in many cases.

Please follow those steps to reproduce the problem:

Let's deploy a test api:

  api = First @ CloudDeploy @ Delayed @ HTTPErrorResponse[404]

Check:
```
  URLRead[api]
```

So far so good

Copy api url string and try

    URLRead["https://www.wolframcloud.com/objects/...."]

Should return 404, nothing unexpected.

Now Quit[] the Kernel and run the manual check again:

    URLRead["https://www.wolframcloud.com/objects/...."]

What? I agree that returning 404 this way may not be the best idea but I expect at least consistent results.

What is more interesting, deploy another api and run manual test for the old url, now it works again...

How to classify this feature? What to call to have stuff initialized/loaded properly?

added 32 characters in body

Source Link

edited Mar 8, 2017 at 11:59

Kuba

137.7k
13
289
751

Loading

Source Link

asked Mar 8, 2017 at 11:29

Kuba

137.7k
13
289
751

Loading

Stack Exchange Network

Return to Question

Inconsistent behavior of HTTPResponse handling

Inconsistent behavior of HTTPResponse handling

Inconsistent HTTPResponse handling

Inconsistent behavior of URLReadHTTPResponse handling

Inconsistent behavior of URLRead

Inconsistent behavior of HTTPResponse handling