dasBlog Work Item Rss Feed

Commented Issue: IIS7 Pipeline mode, strange behavior [3671]

crom84 — Tue, 03 Nov 2009 19:54:31 GMT

When running dasBlog under win 2008 IIS 7 with the IIS7 web.config you'll get really strange behavior when running in Pipeline mode.

Symptoms:
1. Posts will appear and disappear
2. Cache won't invalidate without a application restart
3. If you edit a post direct after posting, the post is "missing"
4...and other strange stuff
5. Uploads over 3mb seems to fail(file lands on server but dasBlog gets nutty)

// Lazze
Comments: ** Comment from web user: crom84 **

I experienced similar behaviour when I went with a new hosting plan.

As it turned out, the new plan was using clustered servers, which DasBlog is not designed to handle.

Created Issue: Getting Error 404.11: double escape sequence error [5303]

crom84 — Tue, 20 Oct 2009 14:10:38 GMT

I have just ported my site to a new server, which is running IIS 7. The DasBlog version I am running is 2.3.9074.18820.

When I click on an article link (e.g. http://www.healthquotes.ca/blog/2009/09/21/2010+Vancouver+Olympics.aspx) I get the following error: "HTTP Error 404.11 - Not Found
The request filtering module is configured to deny a request that contains a double escape sequence."

I don't see a double escape sequence though.

Help!! :)

Commented Issue: IIS7 Pipeline mode, strange behavior [3671]

Domainscanners — Tue, 29 Sep 2009 08:47:34 GMT

Im working on a big site that contains 14 dasBlog installations all running as separate web applications within the same website. Running Win Server 2008 \ IIS7.

I noticed on one blog that when you edited any post it would revert back and loose the changes after a few hours. Spent a long time trying to resolve this and in the end I deleted the blog install completely and reinstalled. I copied the “Content” folder over from a working blog to get some posts in the new blog and now im getting exactly the same problem??? Is something under the hood doing something expected that im unaware of?

Commented Issue: OutOfMemoryException thrown with low # of users in UrlMapperModule Regex

crom84 — Thu, 03 Sep 2009 15:14:19 GMT

After a recent upgrade to release dasBlog 2.3.9074, with default Url Mappings, I frequently receive OutOfMemoryExceptions related to the RegEx matching of incoming Urls under a relatively low load.
Comments: ** Comment from web user: crom84 **

Did you solve thhis problem? I am getting the same error ONLY when I click on the Comment hyperlink to leave a comment.

Created Issue: Trackback response

ReneHezser — Wed, 24 Jun 2009 10:03:35 GMT

Hi,
if I understand the Trackback specification (http://www.sixapart.com/pronet/docs/trackback_spec) correctly, the response for an incoming Trackback request has to be xml.
Currently it is html.
It should be enough to set the content-type: Response.ContentType = "text/xml"

René

Closed Issue: Captcha doesn't work in version 2.2.8279.16125.

paulb — Fri, 19 Jun 2009 02:10:08 GMT

Captcha doesn't work in version 2.2.8279.16125.
Performing a clean install will allow anyone to post comments. Captcha is completely ignored (can type anything or leave blank).
Comments:

fixed

Commented Issue: Captcha doesn't work in version 2.2.8279.16125.

paulb — Fri, 19 Jun 2009 02:09:55 GMT

Captcha doesn't work in version 2.2.8279.16125.
Performing a clean install will allow anyone to post comments. Captcha is completely ignored (can type anything or leave blank).
Comments: ** Comment from web user: paulb **

Fixed in a the current trunk (or maybe 2.3, not sure if it got in)

Closed Issue: his feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

paulb — Fri, 19 Jun 2009 02:07:13 GMT

see -> http://feedvalidator.org/check.cgi?url=http://www.rutlandguttersupply.com/blog/SyndicationService.asmx/GetRss

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.
#

line 2, column 0: Use of unknown namespace: http://www.w3.org/2001/XMLSchema-instance [help]

<rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http:/ ...

#

line 2, column 0: Use of unknown namespace: http://www.w3.org/2001/XMLSchema [help]

<rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http:/ ...

#

line 2, column 0: Use of unknown namespace: http://madskills.com/public/xml/rss/module/pingback/ [help]

<rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http:/ ...

#

line 11, column 49: Email address is missing real name [help]

<managingEditor>blogs@rutlandguttersupply.com</managingEditor>
^

#

line 12, column 44: Email address is missing real name [help]

<webMaster>blogs@rutlandguttersupply.com</webMaster>
^
Comments:

thanks for the suggestion. We will certainly make sure to take a look at these recommendations when we rebuild the feed code. Currently most feedreaders seem to accept the feeds (both rss and atom) without a problem. If you know of any readers, which do have a problem we can have a look at those and see if we can improve the experience in those cases.

Created Issue: his feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

rutlandsupply — Thu, 18 Jun 2009 14:43:28 GMT

Created Issue: Invalid method name 'getrss', method names are case sensitive

rutlandsupply — Thu, 18 Jun 2009 14:31:44 GMT

Some of the feed fetchers (crawl-66-249-70-200.googlebot.com) are converting the syndication rss from ../blog/SyndicationService.asmx/GetRss to ../blog/syndicationservice.asmx/getrss and I get server - access errors. If you manually enter ../blog/syndicationservice.asmx/getrss the error page says:

Invalid method name 'getrss', method names are case sensitive. The method name 'GetRss' with the same name but different casing was found.
Parameter name: methodName

How can you eliminate the case sensitivity and have both uppercase and lower case work reliably? Having the same problem with ../getatom attempts

Error Message: Server error

Requested Page: /blog/syndicationservice.asmx/getrss

Date

Host

Referrer

Browser

Platform
1. Friday, April 24, 2009 at 10:48 p.m. crawl-66-249-70-200.googlebot.com None Googlebot Unknown
2. Friday, April 24, 2009 at 10:49 p.m. crawl-66-249-70-200.googlebot.com None Googlebot Unknown
3. Friday, April 24, 2009 at 10:50 p.m. crawl-66-249-70-200.googlebot.com None Googlebot Unknown
4. Friday, April 24, 2009 at 10:51 p.m. fe03.sitex.search.ac2.yahoo.com None Yahoo Unknown
5. Friday, April 24, 2009 at 10:51 p.m. crawl-66-249-70-200.googlebot.com None Googlebot Unknown
6. Thursday, April 30, 2009 at 4:43 p.m. ec2-67-202-28-213.compute-1.amazonaws.com None AideRSS Unknown
7. Thursday, April 30, 2009 at 4:43 p.m. 38.99.68.206 None FriendFeedBot Unknown
8. Thursday, April 30, 2009 at 4:44 p.m. 79-99-6-106.serverhotell.net None Twingly Recon Unknown
9. Thursday, April 30, 2009 at 4:44 p.m. 79-99-6-106.serverhotell.net None Twingly Recon Unknown
10. Thursday, April 30, 2009 at 4:45 p.m. ec2-67-202-38-4.compute-1.amazonaws.com None uberbot Unknown
11. Thursday, April 30, 2009 at 4:46 p.m. mojito.smartwebsearching.be None PycURL Unknown
12. Thursday, April 30, 2009 at 4:46 p.m. 38.99.68.206 None FriendFeedBot Unknown
13. Thursday, April 30, 2009 at 4:47 p.m. 216-24-131-119.viawest.net None Firefox Windows XP
14. Thursday, April 30, 2009 at 4:47 p.m. 216-24-131-119.viawest.net None Firefox Windows XP
15. Thursday, April 30, 2009 at 4:47 p.m. 216-24-131-119.viawest.net None Firefox Windows XP
16. Thursday, April 30, 2009 at 7:49 p.m. ec2-75-101-161-1.compute-1.amazonaws.com None Firefox Macintosh
17. Saturday, May 2, 2009 at 11:41 a.m. 38.99.68.205 None FriendFeedBot Unknown
18. Saturday, May 2, 2009 at 12:42 p.m. 38.99.68.205 None FriendFeedBot Unknown
19. Saturday, May 2, 2009 at 1:42 p.m. 38.99.68.205 None FriendFeedBot Unknown
20. Saturday, May 2, 2009 at 2:43 p.m. 38.99.68.205 None FriendFeedBot Unknown
21. Saturday, May 2, 2009 at 3:43 p.m. 38.99.68.205 None FriendFeedBot Unknown
22. Saturday, May 2, 2009 at 4:10 p.m. ubuntu820131.aspadmin.net None Firefox Windows NT
23. Saturday, May 2, 2009 at 4:43 p.m. 38.99.68.205 None FriendFeedBot Unknown
24. Sunday, May 3, 2009 at 9:31 p.m. fw01-620.technorati.com None Technoratibot Unknown
25. Tuesday, May 5, 2009 at 12:00 p.m. fw01-620.technorati.com None Technoratibot Unknown
26. Tuesday, May 12, 2009 at 11:41 a.m. htproxy1.ops.re4.yahoo.net None YahooFeedSeeker Unknown
27. Tuesday, May 12, 2009 at 11:42 a.m. 64.233.172.6 None Feedfetcher-Google; Unknown
28. Tuesday, May 12, 2009 at 2:15 p.m. fe-3-28.cr01-200p-sfo.unitedlayer.com None Pageflakes Windows NT
29. Tuesday, May 12, 2009 at 2:16 p.m. fe-3-28.cr01-200p-sfo.unitedlayer.com None Pageflakes Windows NT
30. Tuesday, May 12, 2009 at 2:17 p.m. htproxy2.ops.sp1.yahoo.net None YahooFeedSeeker Unknown
31. Tuesday, May 12, 2009 at 3:19 p.m. fe-3-28.cr01-200p-sfo.unitedlayer.com None Pageflakes Windows NT
32. Tuesday, May 12, 2009 at 3:19 p.m. fe-3-28.cr01-200p-sfo.unitedlayer.com None Pageflakes Windows NT
33. Tuesday, May 12, 2009 at 3:20 p.m. fe-3-28.cr01-200p-sfo.unitedlayer.com None Pageflakes Windows NT
34. Tuesday, May 12, 2009 at 3:20 p.m. fe-3-28.cr01-200p-sfo.unitedlayer.com None Pageflakes Windows NT
35. Tuesday, May 12, 2009 at 3:20 p.m. fe-3-28.cr01-200p-sfo.unitedlayer.com None Pageflakes Windows NT
36. Tuesday, May 12, 2009 at 3:26 p.m. fe-3-28.cr01-200p-sfo.unitedlayer.com None Pageflakes Windows NT
37. Tuesday, May 12, 2009 at 3:26 p.m. fe-3-28.cr01-200p-sfo.unitedlayer.com None Pageflakes Windows NT
38. Tuesday, May 12, 2009 at 3:46 p.m. htproxy2.ops.sp1.yahoo.net None YahooFeedSeeker Unknown
39. Tuesday, May 12, 2009 at 4:30 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
40. Tuesday, May 12, 2009 at 4:32 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
41. Tuesday, May 12, 2009 at 4:48 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
42. Tuesday, May 12, 2009 at 4:49 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
43. Tuesday, May 12, 2009 at 7:49 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
44. Tuesday, May 12, 2009 at 7:50 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
45. Tuesday, May 12, 2009 at 7:51 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
46. Tuesday, May 12, 2009 at 7:52 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
47. Tuesday, May 12, 2009 at 10:52 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
48. Tuesday, May 12, 2009 at 10:53 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
49. Tuesday, May 12, 2009 at 10:54 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
50. Tuesday, May 12, 2009 at 10:55 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
51. Wednesday, May 13, 2009 at 1:55 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
52. Wednesday, May 13, 2009 at 1:56 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
53. Wednesday, May 13, 2009 at 1:57 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
54. Wednesday, May 13, 2009 at 1:58 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
55. Wednesday, May 13, 2009 at 4:58 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
56. Wednesday, May 13, 2009 at 4:59 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
57. Wednesday, May 13, 2009 at 5:00 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
58. Wednesday, May 13, 2009 at 5:01 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
59. Wednesday, May 13, 2009 at 8:01 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
60. Wednesday, May 13, 2009 at 8:02 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
61. Wednesday, May 13, 2009 at 8:03 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
62. Wednesday, May 13, 2009 at 8:04 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
63. Wednesday, May 13, 2009 at 11:04 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
64. Wednesday, May 13, 2009 at 11:05 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
65. Wednesday, May 13, 2009 at 11:06 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
66. Wednesday, May 13, 2009 at 11:11 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
67. Wednesday, May 13, 2009 at 2:24 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
68. Wednesday, May 13, 2009 at 2:25 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
69. Wednesday, May 13, 2009 at 2:26 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
70. Wednesday, May 13, 2009 at 2:38 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
71. Wednesday, May 13, 2009 at 5:38 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
72. Wednesday, May 13, 2009 at 5:39 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
73. Wednesday, May 13, 2009 at 5:40 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
74. Wednesday, May 13, 2009 at 5:41 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
75. Wednesday, May 13, 2009 at 8:42 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
76. Wednesday, May 13, 2009 at 8:43 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
77. Wednesday, May 13, 2009 at 9:21 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
78. Wednesday, May 13, 2009 at 9:23 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
79. Thursday, May 14, 2009 at 12:23 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
80. Thursday, May 14, 2009 at 12:24 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
81. Thursday, May 14, 2009 at 12:25 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
82. Thursday, May 14, 2009 at 12:26 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
83. Thursday, May 14, 2009 at 3:26 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
84. Thursday, May 14, 2009 at 3:27 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
85. Thursday, May 14, 2009 at 3:28 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
86. Thursday, May 14, 2009 at 3:29 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
87. Thursday, May 14, 2009 at 6:29 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
88. Thursday, May 14, 2009 at 6:30 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
89. Thursday, May 14, 2009 at 6:31 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
90. Thursday, May 14, 2009 at 6:32 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
91. Thursday, May 14, 2009 at 9:32 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
92. Thursday, May 14, 2009 at 9:35 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
93. Thursday, May 14, 2009 at 9:36 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
94. Thursday, May 14, 2009 at 9:37 a.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
95. Thursday, May 14, 2009 at 12:37 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
96. Thursday, May 14, 2009 at 6:12 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
97. Thursday, May 14, 2009 at 6:13 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
98. Thursday, May 14, 2009 at 6:14 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
99. Thursday, May 14, 2009 at 9:14 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown
100. Thursday, May 14, 2009 at 9:15 p.m. rate-limited-proxy-72-14-199-45.google.com None Feedfetcher-Google; Unknown

.
.

789. Wednesday, June 10, 2009 at 3:25 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
790. Wednesday, June 10, 2009 at 6:26 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
791. Wednesday, June 10, 2009 at 6:27 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
792. Wednesday, June 10, 2009 at 6:28 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
793. Wednesday, June 10, 2009 at 6:29 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
794. Wednesday, June 10, 2009 at 7:04 a.m. ec2-67-202-41-3.compute-1.amazonaws.com None Internet Archive Unknown
795. Wednesday, June 10, 2009 at 7:05 a.m. ec2-67-202-41-3.compute-1.amazonaws.com None Internet Archive Unknown
796. Wednesday, June 10, 2009 at 9:29 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
797. Wednesday, June 10, 2009 at 9:30 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
798. Wednesday, June 10, 2009 at 9:38 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
799. Wednesday, June 10, 2009 at 10:21 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
800. Wednesday, June 10, 2009 at 1:21 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
801. Wednesday, June 10, 2009 at 1:24 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
802. Wednesday, June 10, 2009 at 1:25 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
803. Wednesday, June 10, 2009 at 1:26 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
804. Wednesday, June 10, 2009 at 4:26 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
805. Wednesday, June 10, 2009 at 4:30 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
806. Wednesday, June 10, 2009 at 4:31 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
807. Wednesday, June 10, 2009 at 4:35 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
808. Wednesday, June 10, 2009 at 10:18 p.m. 80.128.188.72.cfl.res.rr.com None Safari Macintosh
809. Wednesday, June 10, 2009 at 10:47 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
810. Wednesday, June 10, 2009 at 11:10 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
811. Wednesday, June 10, 2009 at 11:11 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
812. Wednesday, June 10, 2009 at 11:12 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
813. Wednesday, June 10, 2009 at 11:29 p.m. crawl-66-249-72-132.googlebot.com None Googlebot Unknown
814. Wednesday, June 10, 2009 at 11:30 p.m. crawl-66-249-72-132.googlebot.com None Googlebot Unknown
815. Wednesday, June 10, 2009 at 11:31 p.m. crawl-66-249-72-132.googlebot.com None Googlebot Unknown
816. Wednesday, June 10, 2009 at 11:32 p.m. crawl-66-249-72-132.googlebot.com None Googlebot Unknown
817. Wednesday, June 10, 2009 at 11:47 p.m. crawl-66-249-72-132.googlebot.com None Googlebot Unknown
818. Wednesday, June 10, 2009 at 11:48 p.m. crawl-66-249-72-132.googlebot.com None Googlebot Unknown
819. Wednesday, June 10, 2009 at 11:49 p.m. crawl-66-249-72-132.googlebot.com None Googlebot Unknown
820. Wednesday, June 10, 2009 at 11:50 p.m. crawl-66-249-72-132.googlebot.com None Googlebot Unknown
821. Thursday, June 11, 2009 at 2:12 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
822. Thursday, June 11, 2009 at 2:13 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
823. Thursday, June 11, 2009 at 2:14 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
824. Thursday, June 11, 2009 at 2:15 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
825. Thursday, June 11, 2009 at 5:15 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
826. Thursday, June 11, 2009 at 5:16 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
827. Thursday, June 11, 2009 at 5:17 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
828. Thursday, June 11, 2009 at 5:18 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
829. Thursday, June 11, 2009 at 8:03 a.m. ec2-67-202-41-3.compute-1.amazonaws.com None Internet Archive Unknown
830. Thursday, June 11, 2009 at 8:18 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
831. Thursday, June 11, 2009 at 8:19 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
832. Thursday, June 11, 2009 at 8:20 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
833. Thursday, June 11, 2009 at 8:21 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
834. Thursday, June 11, 2009 at 11:21 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
835. Thursday, June 11, 2009 at 11:22 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
836. Thursday, June 11, 2009 at 11:23 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
837. Thursday, June 11, 2009 at 11:24 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
838. Thursday, June 11, 2009 at 2:30 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
839. Thursday, June 11, 2009 at 2:31 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
840. Thursday, June 11, 2009 at 2:32 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
841. Thursday, June 11, 2009 at 2:33 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
842. Thursday, June 11, 2009 at 5:33 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
843. Thursday, June 11, 2009 at 5:34 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
844. Thursday, June 11, 2009 at 5:35 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
845. Thursday, June 11, 2009 at 5:36 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
846. Thursday, June 11, 2009 at 8:39 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
847. Thursday, June 11, 2009 at 8:40 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
848. Thursday, June 11, 2009 at 8:41 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
849. Thursday, June 11, 2009 at 8:42 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
850. Thursday, June 11, 2009 at 9:26 p.m. ec2-67-202-41-3.compute-1.amazonaws.com None Internet Archive Unknown
851. Thursday, June 11, 2009 at 11:42 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
852. Thursday, June 11, 2009 at 11:48 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
853. Thursday, June 11, 2009 at 11:49 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
854. Thursday, June 11, 2009 at 11:50 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
855. Friday, June 12, 2009 at 2:51 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
856. Friday, June 12, 2009 at 2:52 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
857. Friday, June 12, 2009 at 2:53 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
858. Friday, June 12, 2009 at 3:02 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
859. Friday, June 12, 2009 at 6:02 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
860. Friday, June 12, 2009 at 6:04 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
861. Friday, June 12, 2009 at 6:05 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
862. Friday, June 12, 2009 at 6:06 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
863. Friday, June 12, 2009 at 9:07 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
864. Friday, June 12, 2009 at 9:08 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
865. Friday, June 12, 2009 at 9:09 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
866. Friday, June 12, 2009 at 9:10 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
867. Friday, June 12, 2009 at 12:10 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
868. Friday, June 12, 2009 at 12:11 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
869. Friday, June 12, 2009 at 12:12 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
870. Friday, June 12, 2009 at 12:13 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
871. Friday, June 12, 2009 at 3:20 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
872. Friday, June 12, 2009 at 3:21 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
873. Friday, June 12, 2009 at 3:22 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
874. Friday, June 12, 2009 at 3:23 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
875. Friday, June 12, 2009 at 5:57 p.m. ec2-67-202-41-3.compute-1.amazonaws.com None Internet Archive Unknown
876. Friday, June 12, 2009 at 6:23 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
877. Friday, June 12, 2009 at 6:24 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
878. Friday, June 12, 2009 at 6:26 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
879. Friday, June 12, 2009 at 6:27 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
880. Friday, June 12, 2009 at 9:27 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
881. Friday, June 12, 2009 at 9:28 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
882. Friday, June 12, 2009 at 9:29 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
883. Friday, June 12, 2009 at 9:30 p.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
884. Saturday, June 13, 2009 at 12:30 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
885. Saturday, June 13, 2009 at 12:31 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
886. Saturday, June 13, 2009 at 12:32 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
887. Saturday, June 13, 2009 at 12:33 a.m. rate-limited-proxy-72-14-199-4.google.com None Feedfetcher-Google; Unknown
888. Saturday, June 13, 2009 at 3:37 a.m. ec2-67-202-41-3.compute-1.amazonaws.com None Internet Archive Unknown

Created Issue: Problem when using the object tag

Morppk — Wed, 17 Jun 2009 07:10:53 GMT

The following affects DASBlog via Internet Explorer

Error: The following steps may stop a DASBlog site from being accessed via Internet Explorer.

Select [ Add Entry ]

Enter a Title e.g. Any Title

And for the first line of the content add the following line.

<object type=text/html data="www.google.com"></object>

or you can enter it in the following format

<object type=text/html data="www.google.com"></object>

Because the address has not been prefixed with http:// DASblog adds its own prefix, which results in a url of

http://[das blog host]/dasblog/www.google.com (which is invalid)

Select Publish entry and Save

Now if you are using Internet Explorer, DASBlog tries to go to that page every time the home page is visited.

DAS Blog can't be used in internet explorer as it keeps going to the incorrect address.
Also it can't be edited in using Internet Explorer meaning that the site can not be used.

Firefox can be used to delete the entry.

Commented Issue: How to translate dasBlog?

persa — Thu, 14 May 2009 22:02:25 GMT

I'm trying to translate dasBlog to brazilian portuguese. I'm translating de file StringTables.resx but the text don't change in the site...

obs.: I translated the theme files, create a StringTable.PT-BR.resx and Create a pt-br.xml
Comments: ** Comment from web user: persa **

You have to rebuild dasBlog to get the compiled resources that is needed for it to show up in the UI.

Closed Issue: Login Fails When EncryptLoginPassword set True in 2.3.9074.18820

tomwatts — Tue, 28 Apr 2009 04:10:22 GMT

I installed 2.3.9074.18820 today from scratch and found I was unable to log in. On IE7 there is no error on the client and the log file displays an "Audit: SecurityFailure Longon with username XXX from IP XXX" message. On IE8 there is an error in the javascript "object expected" on the line "password = net_md5(password); // this makes it superchallenged!!" which in generated in the codebehind for the login box usercontrol: https://dasblog.svn.codeplex.com/svn/trunk/source/newtelligence.DasBlog.Web/LoginBox.ascx.cs. Debugging on the client shows net_md5 is undefined.

Notably, I have never had dasBlog installed before so I am wondering if the script that defines net_md5 is not being included/executed for first timers? Setting EncryptLoginPassword false (which omits this script) allows me to log in fine. Also, I can login OK from Live Writer regardless.
Comments: This issue is closed, the similar issue reported by Tom Watts is peculiar to his installation also, and not a dasBlog issue.

Commented Issue: Login Fails When EncryptLoginPassword set True in 2.3.9074.18820

whirly — Tue, 28 Apr 2009 02:29:12 GMT

OK I've cracked it. The dasBlog code is fine. The problem was the scripts directory was empty on my server! Why? Because I unzipped from a network share. IE Enhanced Security kicked in and silently (GRRR!) prevented the .js files from being extracted. No error messages, nothing! Copying the zip to the C: drive, unblocking and then extracting fixed the problem. This issue can be closed.

Commented Issue: Login Fails When EncryptLoginPassword set True in 2.3.9074.18820

AlexanderGross — Tue, 28 Apr 2009 00:47:33 GMT

Is https://dasblog.svn.codeplex.com/svn/trunk/source/newtelligence.DasBlog.Web/scripts/md5.js included somewhere in login form (<script> elemtent)? If so, can you download it directly using your browser and wget? What's the file's content type as reported by the server?

Commented Issue: Login Fails When EncryptLoginPassword set True in 2.3.9074.18820

tomwatts — Tue, 28 Apr 2009 00:27:30 GMT

I don't have time to do much else, but I can confirm this is a real problem with 2.3, in fact it appears the configuration menu application does edit the password regardless of Encription or not. Of course you can edit the file manually i the interim, but not from the dasBlog GUI.
Tom Watts

Created Issue: Login Fails When EncryptLoginPassword set True in 2.3.9074.18820

whirly — Wed, 22 Apr 2009 18:25:13 GMT

Created Issue: OutOfMemoryException thrown with low # of users in UrlMapperModule Regex

cballance — Wed, 08 Apr 2009 19:22:25 GMT

After a recent upgrade to release dasBlog 2.3.9074, with default Url Mappings, I frequently receive OutOfMemoryExceptions related to the RegEx matching of incoming Urls under a relatively low load.

Commented Issue: Support/Document publishing to Windows Azure

paulb — Sat, 14 Mar 2009 16:54:05 GMT

I'd love to use Windows Azure to host a dasBlog based site.
Comments: ** Comment from web user: paulb **

Working on supporting Azure

Closed Issue: Enabling of CoComment causes javascript error

paulb — Sat, 14 Mar 2009 16:52:29 GMT

NOTE: The code below is still in progress and is untested.

When CoComment is enabled a javescript error occurs with a message of 'coco' is undefined. I have started looking in to this and it appears that cocomment has changed their API. So far I have begun to implement a fix in my implementation that requires the following changes.

this to be added to the default.aspx.cs, so that CoComment can validate that you are the site owner, which means a field needs to be added to the SiteConfig to supply your CoCoUsername

if (SiteConfig.EnableCoComment)
{
this.ClientScript.RegisterClientScriptBlock(this.GetType(), "CoCommentValidate", @"
<script type=""text/javascript"">var cocositeowner=""CoCoUsername"";</script>");
}

I have changed the code in the CommentViewBox.ascx.cs to
if (Page.ClientScript.IsClientScriptIncludeRegistered("cocoDefinition.js") == false && requestPage.SiteConfig.EnableCoComment == true)
{
Page.ClientScript.RegisterClientScriptInclude("cocoDefinition.js", "~/scripts/cocoDefinition.js");
}
if (Page.ClientScript.IsClientScriptBlockRegistered(this.GetType(), "coCommentScript") == false && requestPage.SiteConfig.EnableCoComment == true)
{
string coCommentScript = String.Format(@"

<script type=""text/javascript"">

var blogTool = ""DasBlog"";
var blogURL = ""{0}"";
var blogTitle = ""{1}"";
var postURL = ""{2}"";
var postTitle = ""{3}"";
var commentAuthorFieldName = ""{4}"";
var commentAuthorLoggedIn = false;
var commentFormID = ""mainForm"";
var commentTextFieldName = ""{5}"";
var commentButtonName = ""{6}"";

coco = createCocoDefinition(blogTool, blogUrl, blogTitle,
postUrl, postTitle, commentAuthorFieldName, commentFormID,
commentTextFieldName, commentButtonName);

</script>

<script id=""cocomment-fetchlet""
src=""http://www.cocomment.com/js/enabler.js"" type=""text/javascript""> // this activates coComment </script>
",
requestPage.SiteConfig.Root,
Server.HtmlEncode(requestPage.SiteConfig.Title),
Request.Url.ToString(),
Server.HtmlEncode(entry.Title),
this.name.ClientID,
this.comment.UniqueID,
this.add.ClientID
);
Page.ClientScript.RegisterClientScriptBlock(this.GetType(), "coComment", coCommentScript);

I've also added the cocoDefinition.js file to the scripts folder containing the following code:
// this ensures coComment gets the correct values
function createCocoDefinition(blogTool, blogUrl, blogTitle,
postUrl, postTitle, commentAuthorFieldName, commentFormID,
commentTextFieldName, commentButtonName)
{
return {
tool : blogTool,
siteurl : blogUrl,
sitetitle : blogTitle,
pageurl : postUrl,
pagetitle : postTitle,
author : commentAuthorFieldName,
formID : commentFormID,
textareaID : commentTextFieldName,
buttonID : commentButtonName
};
}
Comments: Fixed.